➜

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 pablogsal
Recipients a-j-buxton, augustogoulart, pablogsal, rhettinger, ronaldoussoren, serhiy.storchaka, taleinat, terry.reedy, vstinner
Date 2018-11-28.22:53:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543445602.14.0.788709270274.issue33930@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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);
  }
}
History
Date User Action Args
2018-11-28 22:53:22pablogsalsetrecipients: + pablogsal, rhettinger, terry.reedy, ronaldoussoren, vstinner, taleinat, serhiy.storchaka, augustogoulart, a-j-buxton
2018-11-28 22:53:22pablogsalsetmessageid: <1543445602.14.0.788709270274.issue33930@psf.upfronthosting.co.za>
2018-11-28 22:53:22pablogsallinkissue33930 messages
2018-11-28 22:53:22pablogsalcreate