Skip to content
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

bpo-36763: Add PyMemAllocatorName #13387

Merged
merged 1 commit into from
May 17, 2019
Merged

bpo-36763: Add PyMemAllocatorName #13387

merged 1 commit into from
May 17, 2019

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented May 17, 2019

  • Add PyMemAllocatorName enum
  • _PyPreConfig.allocator type becomes PyMemAllocatorName, instead of
    char*
  • Remove _PyPreConfig_Clear()
  • Add _PyMem_GetAllocatorName()
  • Rename _PyMem_GetAllocatorsName() to
    _PyMem_GetCurrentAllocatorName()
  • Remove _PyPreConfig_SetAllocator(): just call
    _PyMem_SetupAllocators() directly, we don't have do reallocate the
    configuration with the new allocator anymore!
  • _PyPreConfig_Write() parameter becomes const, as it should be in
    the first place!

https://bugs.python.org/issue36763

* Add PyMemAllocatorName enum
* _PyPreConfig.allocator type becomes PyMemAllocatorName, instead of
  char*
* Remove _PyPreConfig_Clear()
* Add _PyMem_GetAllocatorName()
* Rename _PyMem_GetAllocatorsName() to
  _PyMem_GetCurrentAllocatorName()
* Remove _PyPreConfig_SetAllocator(): just call
  _PyMem_SetupAllocators() directly, we don't have do reallocate the
  configuration with the new allocator anymore!
* _PyPreConfig_Write() parameter becomes const, as it should be in
  the first place!
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