➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author flub
Recipients BreamoreBoy, flub, loewis, neologix, pitrou, sable, tim.peters
Date 2011-04-29.16:26:57
SpamBayes Score 5.642308e-06
Marked as misclassified No
Message-id <BANLkTi=hAYpBif4fWtaQOWbxa_ugZLxNOg@mail.gmail.com>
In-reply-to <1304093795.3587.7.camel@localhost.localdomain>
Content 
On 29 April 2011 17:16, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
>> Yes, I was probably not clear:
>> When --with-dlmalloc is activated, PyMem_MALLOC/PyMem_Malloc will call
>> dlmalloc, PyMem_REALLOC/PyMem_Realloc will call dlrealloc and
>> PyMem_FREE/PyMem_Free will call dlfree.
>>
>> While calls to malloc/free/realloc will use the platform implementation.
>
> I'm not sure why you would want that. If dlmalloc is clearly superior,
> why not use it for all allocations inside the application (not only
> Python ones)?

For the same reason that extension modules can choose between
PyMem_Malloc and plain malloc (or whatever else).  Python has never
forced it's malloc on extension modules why should it now?
History
Date User Action Args
2011-04-29 16:26:58flubsetrecipients: + flub, tim.peters, loewis, pitrou, sable, neologix, BreamoreBoy
2011-04-29 16:26:57flublinkissue3526 messages
2011-04-29 16:26:57flubcreate