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 vstinner
Recipients atuining, eric.snow, izbyshev, lemburg, scoder, serhiy.storchaka, tim.peters, vstinner
Date 2018-11-20.23:20:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Stefan Behnel:
> Making _PyGC_FINALIZED() internal broke Cython ( It's used in the finaliser implementation (, to determine if an object for which tp_dealloc() is called has already been finalised or whether we have to do it. I'm not sure how to deal with this on our side now. Any clue?

I wrote PR 10626 to add _PyGC_FINALIZED() back to the C API.

My intent was only to remove _PyObject_GC_TRACK(o) and _PyObject_GC_UNTRACK(o) from the public C API.

I didn't expect that anyone would use _PyGC_FINALIZED() :-)
Date User Action Args
2018-11-20 23:20:10vstinnersetrecipients: + vstinner, lemburg, tim.peters, atuining, scoder, eric.snow, serhiy.storchaka, izbyshev
2018-11-20 23:20:10vstinnersetmessageid: <>
2018-11-20 23:20:10vstinnerlinkissue35081 messages
2018-11-20 23:20:10vstinnercreate