Skip to content

bpo-36142: Add _PyPreConfig_SetAllocator() #12187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 6, 2019
Merged

bpo-36142: Add _PyPreConfig_SetAllocator() #12187

merged 1 commit into from
Mar 6, 2019

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Mar 5, 2019

  • _PyPreConfig_Write() now reallocates the pre-configuration with the
    new memory allocator.
  • It is no longer needed to force the "default raw memory allocator"
    to clear pre-configuration and core configuration. Simplify the
    code.
  • _PyPreConfig_Write() now does nothing if called after
    Py_Initialize(): no longer check if the allocator is the same.
  • Remove _PyMem_GetDebugAllocatorsName(): dev mode sets again
    allocator to "debug".

https://bugs.python.org/issue36142

* _PyPreConfig_Write() now reallocates the pre-configuration with the
  new memory allocator.
* It is no longer needed to force the "default raw memory allocator"
  to clear pre-configuration and core configuration. Simplify the
  code.
* _PyPreConfig_Write() now does nothing if called after
  Py_Initialize(): no longer check if the allocator is the same.
* Remove _PyMem_GetDebugAllocatorsName(): dev mode sets again
  allocator to "debug".
@vstinner vstinner merged commit c656e25 into python:master Mar 6, 2019
@vstinner vstinner deleted the preparse13 branch March 6, 2019 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants