Pablo Galindo Salgado <pablog...@gmail.com> added the comment:
> Can someone please explain me why this change has any impact? Does it mean > that _PyObject_GC_UNTRACK() macro has a bug? Interestingly, this lonely and perplexing comment is left in PyObject_GC_UnTrack (the function): void PyObject_GC_UnTrack(void *op) { /* Obscure: the Py_TRASHCAN mechanism requires that we be able to * call PyObject_GC_UnTrack twice on an object. */ if (_PyObject_GC_IS_TRACKED(op)) { _PyObject_GC_UNTRACK(op); } } ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33930> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com