Skip to content

Commit 638ac0e

Browse files
committed
Remove Py_TPFLAGS_HAVE_FINALIZE related documentation
1 parent fafa378 commit 638ac0e

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

Doc/c-api/typeobj.rst

-20
Original file line numberDiff line numberDiff line change
@@ -1200,20 +1200,6 @@ and :c:data:`PyType_Type` effectively act as defaults.)
12001200
set appropriately, or the code that interacts with such types
12011201
will behave differently depending on what kind of check is used.
12021202

1203-
1204-
.. c:macro:: Py_TPFLAGS_HAVE_FINALIZE
1205-
1206-
This bit is set when the :c:member:`~PyTypeObject.tp_finalize` slot is present in the
1207-
type structure.
1208-
1209-
.. versionadded:: 3.4
1210-
1211-
.. deprecated:: 3.8
1212-
This flag isn't necessary anymore, as the interpreter assumes the
1213-
:c:member:`~PyTypeObject.tp_finalize` slot is always present in the
1214-
type structure.
1215-
1216-
12171203
.. c:macro:: Py_TPFLAGS_HAVE_VECTORCALL
12181204
12191205
This bit is set when the class implements
@@ -2126,12 +2112,6 @@ and :c:data:`PyType_Type` effectively act as defaults.)
21262112

21272113
.. versionadded:: 3.4
21282114

2129-
.. versionchanged:: 3.8
2130-
2131-
Before version 3.8 it was necessary to set the
2132-
:c:macro:`Py_TPFLAGS_HAVE_FINALIZE` flags bit in order for this field to be
2133-
used. This is no longer required.
2134-
21352115
.. seealso:: "Safe object finalization" (:pep:`442`)
21362116

21372117

0 commit comments

Comments
 (0)