Doc: Update Py_TPFLAGS_HAVE_FINALIZE in docs (GH-96273)

It is now deprecated and the docs should reflect that.
This commit is contained in:
da-woods 2022-08-30 09:31:14 +01:00 committed by GitHub
parent 75177358a6
commit 9625de6fab
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -2005,9 +2005,6 @@ and :c:type:`PyType_Type` effectively act as defaults.)
PyErr_Restore(error_type, error_value, error_traceback); PyErr_Restore(error_type, error_value, error_traceback);
} }
For this field to be taken into account (even through inheritance),
you must also set the :const:`Py_TPFLAGS_HAVE_FINALIZE` flags bit.
Also, note that, in a garbage collected Python, Also, note that, in a garbage collected Python,
:c:member:`~PyTypeObject.tp_dealloc` may be called from :c:member:`~PyTypeObject.tp_dealloc` may be called from
any Python thread, not just the thread which created the object (if the object any Python thread, not just the thread which created the object (if the object
@ -2025,6 +2022,12 @@ and :c:type:`PyType_Type` effectively act as defaults.)
.. versionadded:: 3.4 .. versionadded:: 3.4
.. versionchanged:: 3.8
Before version 3.8 it was necessary to set the
:const:`Py_TPFLAGS_HAVE_FINALIZE` flags bit in order for this field to be
used. This is no longer required.
.. seealso:: "Safe object finalization" (:pep:`442`) .. seealso:: "Safe object finalization" (:pep:`442`)