➜

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 vstinner
Recipients amaury.forgeotdarc, christian.heimes, georg.brandl, kristjan.jonsson, ncoghlan, serhiy.storchaka, vstinner
Date 2013-06-14.23:05:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371251145.24.0.615385065539.issue18203@psf.upfronthosting.co.za>
In-reply-to
Content 
I commited my new API to customize memory allocators:

New changeset 6661a8154eb3 by Victor Stinner in branch 'default':
Issue #3329: Add new APIs to customize memory allocators
http://hg.python.org/cpython/rev/6661a8154eb3

I added PyMem_RawMalloc(), PyMem_RawRealloc() and PyMem_RawFree() in the same commit. These functions are wrappers to malloc/realloc/free which can be called without the GIL held. Using these new functions instead of malloc/realloc/free is interesting because the internal functions can be replaced with PyMem_SetRawAllocators() and many checks are added in debug mode (ex: check for buffer under- and overflow).
History
Date User Action Args
2013-06-14 23:05:45vstinnersetrecipients: + vstinner, georg.brandl, amaury.forgeotdarc, ncoghlan, kristjan.jonsson, christian.heimes, serhiy.storchaka
2013-06-14 23:05:45vstinnersetmessageid: <1371251145.24.0.615385065539.issue18203@psf.upfronthosting.co.za>
2013-06-14 23:05:45vstinnerlinkissue18203 messages
2013-06-14 23:05:45vstinnercreate