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 methane, serhiy.storchaka, thehesiod, vstinner
Date 2017-08-21.11:11:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"like GH-2966, most types with Py_TPFLAGS_HAVE_GC should call PyObject_GC_UnTrack() at top of the tp_dealloc."

Hum, I wasn't aware of that. Writing correctly code for the Python garbage collector is very complex :-/

Maybe it would help to have a short comment, maybe with a link to this issue, on each PyObject_GC_UnTrack().

At the first read, I saw the newly added PyObject_GC_UnTrack() calls as duplicate, and so useless. For example, PyObject_Del() already untracks the object, so it doesn't seem to be needed to explicitly call PyObject_GC_UnTrack() "just before".
Date User Action Args
2017-08-21 11:11:53vstinnersetrecipients: + vstinner, methane, serhiy.storchaka, thehesiod
2017-08-21 11:11:53vstinnersetmessageid: <>
2017-08-21 11:11:53vstinnerlinkissue31095 messages
2017-08-21 11:11:53vstinnercreate