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 brandtbucher, pablogsal, rhettinger, serhiy.storchaka, tim.peters, vstinner
Date 2020-12-03.20:19:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1607026771.46.0.156521374198.issue42536@roundup.psfhosted.org>
In-reply-to
Content
I added some comments in the PR regarding the possibility of forcing the tracking on the visiting function to redirect the cost to gc passes instead of when calling next() but there is another option: not untracking tuples that have refcount == 1.
History
Date User Action Args
2020-12-03 20:19:31pablogsalsetrecipients: + pablogsal, tim.peters, rhettinger, vstinner, serhiy.storchaka, brandtbucher
2020-12-03 20:19:31pablogsalsetmessageid: <1607026771.46.0.156521374198.issue42536@roundup.psfhosted.org>
2020-12-03 20:19:31pablogsallinkissue42536 messages
2020-12-03 20:19:31pablogsalcreate
Morty Proxy This is a proxified and sanitized view of the page, visit original site.