[Python-Dev] PEP 445: Add new APIs to customize Python memory allocators (second round) (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Thu Jun 20 14:16:48 CEST 2013
- Previous message: [Python-Dev] PEP 445: Add new APIs to customize Python memory allocators (second round)
- Next message: [Python-Dev] PEP 445: Add new APIs to customize Python memory allocators (second round)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le Thu, 20 Jun 2013 13:26:52 +0200, Victor Stinner <victor.stinner at gmail.com> a écrit :
Hi,
I changed the PEP 445 according to the discussing on python-dev. Read it online: http://www.python.org/dev/peps/pep-0445/ Changes: * add PyMemAllocatorDomain enum: PYALLOCPYMEMRAW, PYALLOCPYMEM or PYALLOCPYOBJECT
PYMEM_DOMAIN_RAW?
* rename:
- PyMemBlockAllocator structure => PyMemAllocator - PyMemMappingAllocator structure => PyObjectArenaAllocator - PyMemGetMappingAllocator() => PyObjectGetArenaAllocator() - PyMemSetMappingAllocator() => PyObjectSetArenaAllocator() * group get/set functions to only keep 2 functions: PyMemGetAllocator() and PyMemSetAllocator() * PyMemRawMalloc(0) now calls malloc(1) to have a well defined behaviour * PYALLOCPYMEMRAW and PYALLOCPYMEM are now using exactly the same allocator * Add more references for external libraries As expected, most changes occurred in the Proposal section. Full diff: http://hg.python.org/peps/rev/a17ebebe52ca I also updated the implementation attached to: http://bugs.python.org/issue3329 Who is going give the final decision on this PEP? Guido? Another candidate? Victor
- Previous message: [Python-Dev] PEP 445: Add new APIs to customize Python memory allocators (second round)
- Next message: [Python-Dev] PEP 445: Add new APIs to customize Python memory allocators (second round)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]