From: Neil Schemenauer <nascheme@enme.ucalgary.ca>
Date: Wed, 8 May 2002 14:14:41 +0000 (+0000)
Subject: Remove news about PyMalloc_*.  Do we need to say anything about
X-Git-Tag: v2.3c1~5703
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c9abc1de6b6739a75b7eb87711a9ef30db5c682e;p=thirdparty%2FPython%2Fcpython.git

Remove news about PyMalloc_*.  Do we need to say anything about
pymalloc?
---

diff --git a/Misc/NEWS b/Misc/NEWS
index d31e09d8507b..5608af98a8bd 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -216,12 +216,7 @@ C API
 
 - PyType_Ready() accidentally did not inherit tp_is_gc; now it does.
 
-- 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.
+- The PyCore_* family of APIs have been removed.
 
 - The "u#" parser marker will now pass through Unicode objects as-is
   without going through the buffer API.