Searched refs:tp_clear (Results 1 – 9 of 9) sorted by relevance
12 runs tp_clear on all unreachable objects, if an unreachable object is13 resurrected then tp_clear will eventually be called on it (or may already15 historically common bug), tp_clear empties an instance's __dict__, and16 "impossible" AttributeErrors result. At worst, tp_clear leaves behind an44 will call before it's done --tp_clear()). It's not even necessarily that a92 that have already suffered a tp_clear() call. There's no guarantee that an93 object is in a sane state after tp_clear(). Bad things (including128 defined-- or even predictable --order in which tp_clear() gets called on148 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 …]
767 if ((clear = Py_TYPE(op)->tp_clear) != NULL) { in delete_garbage()
1509 return PyDict_Type.tp_clear((PyObject *)dd); in defdict_tp_clear()
365 inquiry tp_clear; member
880 while ((baseclear = base->tp_clear) == subtype_clear) { in subtype_clear()2465 type->tp_clear = subtype_clear; in type_new()3694 (!type->tp_traverse && !type->tp_clear)) {3698 if (type->tp_clear == NULL)3699 type->tp_clear = base->tp_clear;
872 while ((baseclear = base->tp_clear) == subtype_clear) { in subtype_clear()2445 type->tp_clear = subtype_clear; in type_new()3659 (!type->tp_traverse && !type->tp_clear)) {3663 if (type->tp_clear == NULL)3664 type->tp_clear = base->tp_clear;
818 if ((clear = Py_TYPE(op)->tp_clear) != NULL) { in delete_garbage()
1579 return PyDict_Type.tp_clear((PyObject *)dd); in defdict_tp_clear()