➜

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 pitrou
Recipients Yury.Selivanov, jtaylor, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov
Date 2016-02-02.14:53:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <56B0C2DB.9010404@free.fr>
In-reply-to <1454424518.45.0.277729800673.issue26249@psf.upfronthosting.co.za>
Content 
Le 02/02/2016 15:48, STINNER Victor a écrit :
>> What this says is that some internals uses of PyMem_XXX should be replaced with PyObject_XXX.
> 
> Why not changing PyMem_XXX to use the same fast allocator than
PyObject_XXX? (as proposed in this issue)

Why have two sets of functions doing exactly the same thing?
History
Date User Action Args
2016-02-02 14:53:16pitrousetrecipients: + pitrou, rhettinger, vstinner, Yury.Selivanov, jtaylor, serhiy.storchaka, yselivanov
2016-02-02 14:53:16pitroulinkissue26249 messages
2016-02-02 14:53:16pitroucreate