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 serhiy.storchaka
Recipients eli.bendersky, martin.panter, scoder, serhiy.storchaka
Date 2015-11-23.07:57:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448265462.69.0.011933331006.issue25688@psf.upfronthosting.co.za>
In-reply-to
Content
Warning is emitted in destructor, and exceptions in destructors are ignored. Hence turning it into error makes the test passed.

Tests were not correct, here is fixed patch.

Yes, CleanContext does the work. But depending on it looks fragile. CleanContext can be removed after getting rid of all deprecated methods.

I agree that we have to add the close() method to iterparse object. But this is new feature and separate issue.
History
Date User Action Args
2015-11-23 07:57:42serhiy.storchakasetrecipients: + serhiy.storchaka, scoder, eli.bendersky, martin.panter
2015-11-23 07:57:42serhiy.storchakasetmessageid: <1448265462.69.0.011933331006.issue25688@psf.upfronthosting.co.za>
2015-11-23 07:57:42serhiy.storchakalinkissue25688 messages
2015-11-23 07:57:41serhiy.storchakacreate