mirror of https://github.com/python/cpython
Remove news about PyMalloc_*. Do we need to say anything about
pymalloc?
This commit is contained in:
parent
40df710876
commit
c9abc1de6b
|
@ -216,12 +216,7 @@ C API
|
||||||
|
|
||||||
- PyType_Ready() accidentally did not inherit tp_is_gc; now it does.
|
- PyType_Ready() accidentally did not inherit tp_is_gc; now it does.
|
||||||
|
|
||||||
- Objects allocated using the new PyMalloc_New and PyMalloc_NewVar
|
- The PyCore_* family of APIs have been removed.
|
||||||
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 "u#" parser marker will now pass through Unicode objects as-is
|
- The "u#" parser marker will now pass through Unicode objects as-is
|
||||||
without going through the buffer API.
|
without going through the buffer API.
|
||||||
|
|
Loading…
Reference in New Issue