Home Original page

[Python-Dev] RFC: PEP 445: Add new APIs to customize Python memory allocators

Terry Reedy tjreedy at udel.edu
Wed Jun 19 18:13:06 CEST 2013 
On 6/19/2013 11:24 AM, Victor Stinner wrote:
> 2013/6/19 Antoine Pitrou <solipsis at pitrou.net>:
>> Le Tue, 18 Jun 2013 22:40:49 +0200,
>> Victor Stinner <victor.stinner at gmail.com> a écrit :

>>> Only one get/set function for block allocators
>>> ----------------------------------------------
>>>
>>> Replace the 6 functions:
>>>
>>> * ``void PyMem_GetRawAllocator(PyMemBlockAllocator *allocator)``
>>> * ``void PyMem_GetAllocator(PyMemBlockAllocator *allocator)``
>>> * ``void PyObject_GetAllocator(PyMemBlockAllocator *allocator)``
>>> * ``void PyMem_SetRawAllocator(PyMemBlockAllocator *allocator)``
>>> * ``void PyMem_SetAllocator(PyMemBlockAllocator *allocator)``
>>> * ``void PyObject_SetAllocator(PyMemBlockAllocator *allocator)``
>>>
>>> with 2 functions with an additional *domain* argument:
>>>
>>> * ``int PyMem_GetBlockAllocator(int domain, PyMemBlockAllocator
>>> *allocator)``
>>> * ``int PyMem_SetBlockAllocator(int domain, PyMemBlockAllocator
>>> *allocator)``
>>
>> I would much prefer this solution.

I do to. The two names can be remembered as one pair with only get/set 
difference.

-- 
Terry Jan Reedy
More information about the Python-Dev mailing list