Home
last modified time | relevance | path

Searched refs:tp_clear (Results 1 – 11 of 11) sorted by relevance

/external/python/cpython2/Modules/
Dgc_weakref.txt12 runs tp_clear on all unreachable objects, if an unreachable object is
13 resurrected then tp_clear will eventually be called on it (or may already
15 historically common bug), tp_clear empties an instance's __dict__, and
16 "impossible" AttributeErrors result. At worst, tp_clear leaves behind an
44 will call before it's done --tp_clear()). It's not even necessarily that a
92 that have already suffered a tp_clear() call. There's no guarantee that an
93 object is in a sane state after tp_clear(). Bad things (including
128 defined-- or even predictable --order in which tp_clear() gets called on
148 So, to prevent any Python code from running while gc is invoking tp_clear()
158 tp_clear() on weakrefs with callbacks first. Instead the weakref module
[all …]
Dgcmodule.c818 if ((clear = Py_TYPE(op)->tp_clear) != NULL) { in delete_garbage()
D_collectionsmodule.c1635 return PyDict_Type.tp_clear((PyObject *)dd); in defdict_tp_clear()
/external/python/cpython2/Doc/includes/
Dtypestruct.h42 inquiry tp_clear; member
/external/python/cpython2/Doc/c-api/
Dgcsupport.rst21 :c:member:`~PyTypeObject.tp_clear` implementation must also be provided.
155 The :c:member:`~PyTypeObject.tp_clear` handler must be of the :c:type:`inquiry` type, or *NULL*
Dtypeobj.rst433 …the :c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` fields, i.e. if t…
435 …:c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` fields in the subtype…
494 …well as the :c:member:`~PyTypeObject.tp_traverse` and the :c:member:`~PyTypeObject.tp_clear` field…
555 …GC-related fields :c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` are…
617 This field is inherited by subtypes together with :c:member:`~PyTypeObject.tp_clear` and the
619 :c:member:`~PyTypeObject.tp_clear` are all inherited from the base type if they are all zero in
624 .. c:member:: inquiry PyTypeObject.tp_clear
629 … The :c:member:`~PyTypeObject.tp_clear` member function is used to break reference cycles in cyclic
630 … garbage detected by the garbage collector. Taken together, all :c:member:`~PyTypeObject.tp_clear`
632 subtle, and if in any doubt supply a :c:member:`~PyTypeObject.tp_clear` function. For example,
[all …]
/external/python/cpython2/Include/
Dobject.h365 inquiry tp_clear; member
/external/python/cpython2/Objects/
Dtypeobject.c900 while ((baseclear = base->tp_clear) == subtype_clear) { in subtype_clear()
2506 type->tp_clear = subtype_clear; in type_new()
3785 (!type->tp_traverse && !type->tp_clear)) {
3789 if (type->tp_clear == NULL)
3790 type->tp_clear = base->tp_clear;
/external/python/cpython2/Modules/_ctypes/
D_ctypes.c757 return PyType_Type.tp_clear((PyObject *)self); in CDataType_clear()
/external/python/cpython2/Doc/extending/
Dnewtypes.rst1510 0, /* tp_clear */
/external/python/cpython2/Misc/
DHISTORY1033 - Patch #1473132: Improve docs for ``tp_clear`` and ``tp_traverse``.
9186 tp_traverse and tp_clear. The augmented assignment changes result in