➜

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 georg.brandl
Recipients amaury.forgeotdarc, christian.heimes, georg.brandl, kristjan.jonsson, ncoghlan, serhiy.storchaka, vstinner
Date 2013-06-13.17:27:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371144450.95.0.437245067379.issue18203@psf.upfronthosting.co.za>
In-reply-to
Content 
> We have to be careful with the GIL: PyMem_*() functions can only be
> called when holding the GIL.

> Some libraries can be configured to use a custom memory allocators:
> [...]
> We should probably uses these functions to reuse Python allocators 
> (PyMem_Malloc())

I think there's a potential problem here :)
History
Date User Action Args
2013-06-13 17:27:31georg.brandlsetrecipients: + georg.brandl, amaury.forgeotdarc, ncoghlan, kristjan.jonsson, vstinner, christian.heimes, serhiy.storchaka
2013-06-13 17:27:30georg.brandlsetmessageid: <1371144450.95.0.437245067379.issue18203@psf.upfronthosting.co.za>
2013-06-13 17:27:30georg.brandllinkissue18203 messages
2013-06-13 17:27:30georg.brandlcreate