Searched refs:finalizers (Results 1 – 7 of 7) sorted by relevance
537 move_finalizers(PyGC_Head *unreachable, PyGC_Head *finalizers) in move_finalizers() argument552 gc_list_move(gc, finalizers); in move_finalizers()576 move_finalizer_reachable(PyGC_Head *finalizers) in move_finalizer_reachable() argument579 PyGC_Head *gc = finalizers->gc.gc_next; in move_finalizer_reachable()580 for (; gc != finalizers; gc = gc->gc.gc_next) { in move_finalizer_reachable()585 (void *)finalizers); in move_finalizer_reachable()778 handle_finalizers(PyGC_Head *finalizers, PyGC_Head *old) in handle_finalizers() argument780 PyGC_Head *gc = finalizers->gc.gc_next; in handle_finalizers()787 for (; gc != finalizers; gc = gc->gc.gc_next) { in handle_finalizers()796 gc_list_merge(finalizers, old); in handle_finalizers()[all …]
210 __del__ methods is to avoid running finalizers in an arbitrary order).
854 as there are no finalizers implemented in Python (:meth:`__del__` methods).855 When there are such finalizers, the detector exposes the cycles through the
658 Python code (due to finalizers, or weakref callbacks, associated with the
13754 [api] Bring back finalizers on global handles.
2209 - Issue #14548: Make multiprocessing finalizers check pid before
6109 with finalizers. (The "get attribute" and "set attribute" methods