/external/python/cpython2/Modules/ |
D | gc_weakref.txt | 12 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 …]
|
D | gcmodule.c | 815 if ((clear = Py_TYPE(op)->tp_clear) != NULL) { in delete_garbage()
|
D | _collectionsmodule.c | 1649 return PyDict_Type.tp_clear((PyObject *)dd); in defdict_tp_clear()
|
/external/python/cpython3/Modules/ |
D | gc_weakref.txt | 12 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 …]
|
D | _asynciomodule.c | 1447 .tp_clear = (inquiry)FutureObj_clear, 1759 .tp_clear = (inquiry)TaskStepMethWrapper_clear, 1833 .tp_clear = (inquiry)TaskWakeupMethWrapper_clear, 2421 .tp_clear = (inquiry)TaskObj_clear,
|
D | gcmodule.c | 759 if ((clear = Py_TYPE(op)->tp_clear) != NULL) { in delete_garbage()
|
D | _collectionsmodule.c | 2159 return PyDict_Type.tp_clear((PyObject *)dd); in defdict_tp_clear()
|
/external/python/cpython2/Doc/includes/ |
D | typestruct.h | 42 inquiry tp_clear; member
|
/external/python/cpython3/Doc/includes/ |
D | typestruct.h | 42 inquiry tp_clear; member
|
D | custom4.c | 170 .tp_clear = (inquiry) Custom_clear,
|
/external/python/cpython3/Doc/c-api/ |
D | typeobj.rst | 396 …the :c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` fields, i.e. if t… 398 …:c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` fields in the subtype… 442 …GC-related fields :c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` are… 523 This field is inherited by subtypes together with :c:member:`~PyTypeObject.tp_clear` and the 525 :c:member:`~PyTypeObject.tp_clear` are all inherited from the base type if they are all zero in 529 .. c:member:: inquiry PyTypeObject.tp_clear 534 … The :c:member:`~PyTypeObject.tp_clear` member function is used to break reference cycles in cyclic 535 … garbage detected by the garbage collector. Taken together, all :c:member:`~PyTypeObject.tp_clear` 537 subtle, and if in any doubt supply a :c:member:`~PyTypeObject.tp_clear` function. For example, 538 the tuple type does not implement a :c:member:`~PyTypeObject.tp_clear` function, because it's [all …]
|
D | gcsupport.rst | 18 :c:member:`~PyTypeObject.tp_clear` implementation must also be provided. 148 The :c:member:`~PyTypeObject.tp_clear` handler must be of the :c:type:`inquiry` type, or *NULL*
|
/external/python/cpython2/Doc/c-api/ |
D | typeobj.rst | 433 …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 …]
|
D | gcsupport.rst | 21 :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*
|
/external/python/cpython3/Python/ |
D | context.c | 670 .tp_clear = (inquiry)context_tp_clear, 1006 .tp_clear = (inquiry)contextvar_tp_clear, 1140 .tp_clear = (inquiry)token_tp_clear,
|
D | hamt.c | 2624 .tp_clear = (inquiry)hamt_baseiter_tp_clear, \ 2923 .tp_clear = (inquiry)hamt_tp_clear,
|
/external/python/cpython3/Objects/ |
D | typeslots.inc | 52 offsetof(PyHeapTypeObject, ht_type.tp_clear),
|
D | typeobject.c | 1089 while ((baseclear = base->tp_clear) == subtype_clear) { in subtype_clear() 2787 type->tp_clear = subtype_clear; in type_new() 4868 (!type->tp_traverse && !type->tp_clear)) { in inherit_special() 4872 if (type->tp_clear == NULL) in inherit_special() 4873 type->tp_clear = base->tp_clear; in inherit_special()
|
/external/python/cpython2/Include/ |
D | object.h | 365 inquiry tp_clear; member
|
/external/python/cpython3/Include/ |
D | object.h | 388 inquiry tp_clear; member
|
/external/python/cpython2/Objects/ |
D | typeobject.c | 900 while ((baseclear = base->tp_clear) == subtype_clear) { in subtype_clear() 2509 type->tp_clear = subtype_clear; in type_new() 3848 (!type->tp_traverse && !type->tp_clear)) { 3852 if (type->tp_clear == NULL) 3853 type->tp_clear = base->tp_clear;
|
/external/python/cpython3/Doc/extending/ |
D | newtypes.rst | 122 and/or :c:member:`~PyTypeObject.tp_clear`), some of the object's members can have been
|
/external/python/cpython3/Modules/_ctypes/ |
D | _ctypes.c | 785 return PyType_Type.tp_clear((PyObject *)self); in CDataType_clear()
|
/external/python/cpython2/Modules/_ctypes/ |
D | _ctypes.c | 828 return PyType_Type.tp_clear((PyObject *)self); in CDataType_clear()
|
/external/python/cpython2/Doc/extending/ |
D | newtypes.rst | 1514 0, /* tp_clear */
|