[issue40240] Expose public spelling of _PyGC_FINALIZED and _PyGC_SET_FINALIZED?

Eric Cousineau report at bugs.python.org
Thu Apr 9 16:26:21 EDT 2020


Eric Cousineau <eric.cousineau at tri.global> added the comment:

> [...] but I am not sure it makes sense to allow to mark an object as finalized because that could mess with the GC algorithm.

Actually, I would like the opposite, to mark it unfinalized to resurrect the object more than once. PEP 442 from a ways back had this effect (per bpo-32377), and Antoine updated the docs after I filed the issue.

I didn't chime in early enough to snag the "more-than-once" functionality, so I guess this is what I get for dipping into private API without asking to make it public until 2 years later... d'oh!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue40240>
_______________________________________


More information about the Python-bugs-list mailing list