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 ashkop, berker.peksag, ezio.melotti, flox, martin.panter, rbcollins, serhiy.storchaka, vstinner
Date 2015-09-03.03:22:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Okay so I take back my first proposal of restoring the filters in the test suite, which would bring us back to <>.

Also, my second proposal of setting a flag doesn’t look so easy either. The “_warnings” C module caches the filters list in a static variable between module reloads, so it is not so easy to keep a flag recording whether the “warnings” Python module needs to initialize it. I started on a patch, but discovered I would have to make uncomfortable changes to the C module.

So unless anyone has any better ideas, I think Alex’s patch is as good and practical enough. And yes Victor’s change does fix the other half of the problem.
Date User Action Args
2015-09-03 03:22:36martin.pantersetrecipients: + martin.panter, vstinner, rbcollins, ezio.melotti, flox, berker.peksag, serhiy.storchaka, ashkop
2015-09-03 03:22:36martin.pantersetmessageid: <>
2015-09-03 03:22:36martin.panterlinkissue18383 messages
2015-09-03 03:22:35martin.pantercreate