www.python.org/pycon/2005/papers/79/python-memory.pdf http://sourceforge.net/tracker/index.php?func=detail&aid=1123430&group_id=5470&atid=305470 "This is the second version of my Python memory allocator patch. The first version was discussed on the python-dev mailing list here: http://mail.python.org/pipermail/python-dev/2005-January/051255.html This patch enables Python to actually return memory to the system. The current version's memory usage will only grow. This version maintains the same backwards compatability guarantees as the previous version: Calling PyObject_Free with a pointer that was returned by malloc() while NOT holding the GIL will work, and will not corrupt the state of the memory allocator. The patch modifies obmalloc.c. If it is accepted, other modifications to that file are required. In particular, I have not yet updated the WITH_MEMORY_LIMITS implementation, nor have I looked closely at the PYMALLOC_DEBUG code to see what changes (if any) are required." Reproducible: Always Steps to Reproduce:
This is an experimental patch that according to the ML discussion might break threading and possibly other things too. I don't think it's a good idea adding somewhat experimental patches to python, especially not since Gentoo is so dependent on python. So I'll mark it WONTFIX and wait for upstream to add it instead. Thanks for your report.
