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 eli.bendersky, martin.panter, scoder, serhiy.storchaka
Date 2015-11-23.06:08:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448258896.7.0.324980929525.issue25688@psf.upfronthosting.co.za>
In-reply-to
Content
What’s the point of the catch_warnings() and filterwarnings() calls in the tests? They don’t seem to be doing much; I think the CleanContext manager is already enabling warnings. Perhaps you could call simplefilter("error", ResourceWarning) instead.

Also I’m not enthusiastic about the iterparse() API when passing a file name. If it has to stay, maybe there should be an explicit way to clean it up without exhausting the iterator, like a generator.close() method.
History
Date User Action Args
2015-11-23 06:08:16martin.pantersetrecipients: + martin.panter, scoder, eli.bendersky, serhiy.storchaka
2015-11-23 06:08:16martin.pantersetmessageid: <1448258896.7.0.324980929525.issue25688@psf.upfronthosting.co.za>
2015-11-23 06:08:16martin.panterlinkissue25688 messages
2015-11-23 06:08:16martin.pantercreate