This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Eric Cousineau
Recipients Eric Cousineau, docs@python, pitrou
Date 2017-12-19.16:46:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513701998.29.0.213398074469.issue32377@psf.upfronthosting.co.za>
In-reply-to
Content
You're welcome, and thank you for the prompt response!

I will say that it feels a tad odd to only have `tp_finalize` be called once for the entire lifetime of the object, while still having the option of it being resurrected.
Is there any way to somehow "un-mark" the object to enable this workflow that I would like to have?

My current hack is to call `_PyGC_SET_FINALIZED(self, 0)` - may I ask if there is a simpler way to do this?
History
Date User Action Args
2017-12-19 16:46:38Eric Cousineausetrecipients: + Eric Cousineau, pitrou, docs@python
2017-12-19 16:46:38Eric Cousineausetmessageid: <1513701998.29.0.213398074469.issue32377@psf.upfronthosting.co.za>
2017-12-19 16:46:38Eric Cousineaulinkissue32377 messages
2017-12-19 16:46:38Eric Cousineaucreate