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 josh.r
Recipients benhoyt, gvanrossum, josh.r, martin.panter, serhiy.storchaka, vstinner
Date 2016-02-09.00:01:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Adding a ResourceWarning even if the generator is run to completion? That seems... dev hostile. I mean, yes, probably best to document it as best practice to use with with statement, but something simple like `files = sorted(os.scandir('.'), key=lambda x: x.stat().st_mtime)` to get files ordered by modification time (which cleanly runs the generator to exhaustion immediately) should not be raising ResourceWarning in 3.6 when it didn't do so in 3.5, and has minimal risk of leaking in any event.
Date User Action Args
2016-02-09 00:01:11josh.rsetrecipients: + josh.r, gvanrossum, vstinner, benhoyt, martin.panter, serhiy.storchaka
2016-02-09 00:01:11josh.rsetmessageid: <>
2016-02-09 00:01:11josh.rlinkissue25994 messages
2016-02-09 00:01:11josh.rcreate