From c9abc1de6b6739a75b7eb87711a9ef30db5c682e Mon Sep 17 00:00:00 2001 From: Neil Schemenauer Date: Wed, 8 May 2002 14:14:41 +0000 Subject: Remove news about PyMalloc_*. Do we need to say anything about pymalloc? --- Misc/NEWS | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/Misc/NEWS b/Misc/NEWS index d31e09d..5608af9 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. -- cgit v0.12