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 brandtbucher
Recipients brandtbucher, pablogsal, rhettinger, serhiy.storchaka, tim.peters, vstinner
Date 2020-12-03.15:30:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1607009457.87.0.474262026448.issue42536@roundup.psfhosted.org>
In-reply-to
Content
> I add Pablo and Tim who love GC puzzles.

Well, I don’t think the GC is really doing anything wrong here... untracking these sort of tuples likely results in a noticeable reduction in collection times. This code is definitely testing the limits of what is “okay” for us to do with a tuple, and it’s breaking the GC’s (reasonable) assumptions.

I kept digging around, and it appears dict.items() is affected, too (which is a bit scarier). The same fix still works, though.
History
Date User Action Args
2020-12-03 15:30:57brandtbuchersetrecipients: + brandtbucher, tim.peters, rhettinger, vstinner, serhiy.storchaka, pablogsal
2020-12-03 15:30:57brandtbuchersetmessageid: <1607009457.87.0.474262026448.issue42536@roundup.psfhosted.org>
2020-12-03 15:30:57brandtbucherlinkissue42536 messages
2020-12-03 15:30:57brandtbuchercreate