Skip to content

Commit a26cb08

Browse files
remove reference to subtype_delloc
1 parent e29e709 commit a26cb08

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

Doc/extending/extending.rst

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1086,10 +1086,9 @@ user-defined class, and let's further suppose that the class defined a
10861086
:meth:`!__del__` method. If this class instance has a reference count of 1,
10871087
disposing of it will call its :meth:`!__del__` method. Internally,
10881088
:c:func:`PyList_SetItem` calls :c:func:`Py_DECREF` on the replaced item,
1089-
which invokes replaced item's corresponding
1090-
:c:member:`~PyTypeObject.tp_dealloc` function (that is
1091-
:c:func:`subtype_dealloc` in case of Python class instance). During
1092-
deallocation, :c:func:`subtype_dealloc` calls
1089+
which invokes replaced item's corrresponding
1090+
:c:member:`~PyTypeObject.tp_dealloc` function. During
1091+
deallocation, :c:member:`~PyTypeObject.tp_dealloc` calls
10931092
:c:member:`~PyTypeObject.tp_finalize`, which is mapped to the
10941093
:meth:`!__del__` method for class instances (see :pep:`442`). This entire
10951094
sequence happens synchronously within the :c:func:`PyList_SetItem` call.

0 commit comments

Comments
 (0)