Incorrect Misc/NEWS entry
One entry in Misc/NEWS reads: - Objects allocated using the new PyMalloc_New and PyMalloc_NewVar functions will be allocated using pymalloc if it is enabled. These objects should be deallocated using PyMalloc_Del. The PyObject_{New, NewVar,NEW_VAR,Del,DEL} APIs have been changed to always use PyMem_MALLOC and PyMem_FREE, even if pymalloc is enabled. The PyCore_* family of APIs have been removed. I can't find PyMalloc_New anywhere in the source code. Is this perhaps a typo for PyObject_New()? Also, PLAN.txt is still in the top-level directory. Is it still relevant for 2.3, or was everything in it finished for 2.2? --amk
I can't find PyMalloc_New anywhere in the source code. Is this perhaps a typo for PyObject_New()?
I'll let Tim answer that.
Also, PLAN.txt is still in the top-level directory. Is it still relevant for 2.3, or was everything in it finished for 2.2?
Some of what it says is still relevant, alas. My aim is to be able to remove it before 2.3 final ships, but right now I am busy on Zope Corp customer projects. --Guido van Rossum (home page: http://www.python.org/~guido/)
Andrew Kuchling wrote:
One entry in Misc/NEWS reads:
- Objects allocated using the new PyMalloc_New and PyMalloc_NewVar functions will be allocated using pymalloc if it is enabled. These objects should be deallocated using PyMalloc_Del. The PyObject_{New, NewVar,NEW_VAR,Del,DEL} APIs have been changed to always use PyMem_MALLOC and PyMem_FREE, even if pymalloc is enabled. The PyCore_* family of APIs have been removed.
I can't find PyMalloc_New anywhere in the source code. Is this perhaps a typo for PyObject_New()?
Oops, that's written by me and is now totally wrong. PyObject_{New,...} will allocate using pymalloc if it's enabled. Forget about PyMalloc_{New,NewVar}. Neil
participants (3)
-
Andrew Kuchling
-
Guido van Rossum
-
Neil Schemenauer