bpo-32096: Statically initialize the default raw allocator.#4481
bpo-32096: Statically initialize the default raw allocator.#4481ericsnowcurrently wants to merge 5 commits into
Conversation
ncoghlan
left a comment
There was a problem hiding this comment.
In addition to a NEWS entry, it would be preferable to add an explicit test for this to _testembed.c.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
For the explicit test, I'd suggest a dedicated one that just does: We can then consider adding equivalent tests for other "safe before Py_Initialize" APIs in https://bugs.python.org/issue32086 |
Sorry, something went wrong.
a8c4376 to
9584720
Compare
November 21, 2017 17:37
ncoghlan
left a comment
There was a problem hiding this comment.
This looks good to me, but I'm not entirely sure I understand the NEWS entry.
Unless the NEWS entry has typos in it, in which case it makes sense and just needs the typos fixed :)
Sorry, something went wrong.
|
CI failure looks real though - my guess would be an allocator/deallocator mismatch due to Py_Finalize not explicitly reverting back to the default allocator. |
Sorry, something went wrong.
|
This PR has been superseded by PR #4532, which reverts the mem-related globals consolidation. We will revisit a long-term solution later. |
Sorry, something went wrong.
The recent global runtime state consolidation broke pre-init usage of Py_DecodeLocale(). This patch fixes that.
https://bugs.python.org/issue32096