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 martin.panter
Recipients benhoyt, gvanrossum, josh.r, martin.panter, serhiy.storchaka, vstinner
Date 2016-02-09.01:45:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I would be in favour of adding a ResourceWarning in 3.6 if the iterator is garbage collected without being exhausted. But as Josh says, it might be overkill emitting a warning when we already know the iterator has been finished and cleaned up.
Date User Action Args
2016-02-09 01:45:36martin.pantersetrecipients: + martin.panter, gvanrossum, vstinner, benhoyt, serhiy.storchaka, josh.r
2016-02-09 01:45:36martin.pantersetmessageid: <>
2016-02-09 01:45:36martin.panterlinkissue25994 messages
2016-02-09 01:45:35martin.pantercreate