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 tim.peters
Recipients Guido.van.Rossum, gvanrossum, inglesp, larry, pitrou, tim.golden, tim.peters, vstinner
Date 2014-05-07.23:25:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399505115.03.0.0482505920731.issue21435@psf.upfronthosting.co.za>
In-reply-to
Content
finalize4.patch repairs the comment typos, adds a new comment, and removes the unused `old` argument.  I think the code is ready to ship with this.  

I still don't have a reasonably simple fails-before-works-after test case.    But that doesn't bother me much, since "the problem" is obvious once it's been seen, and the patch obviously fixes it, and any way of trying to provoke this from pure Python will rely on implementation accidents to get exactly the right pieces of cyclic trash in exactly the right order in gc's internal lists.  Still, hope springs eternal ;-)
History
Date User Action Args
2014-05-07 23:25:15tim.peterssetrecipients: + tim.peters, gvanrossum, pitrou, vstinner, larry, tim.golden, inglesp, Guido.van.Rossum
2014-05-07 23:25:15tim.peterssetmessageid: <1399505115.03.0.0482505920731.issue21435@psf.upfronthosting.co.za>
2014-05-07 23:25:15tim.peterslinkissue21435 messages
2014-05-07 23:25:14tim.peterscreate