➜

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 martin.panter, python-dev, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-11-22.01:00:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479776420.2.0.758218535429.issue28688@psf.upfronthosting.co.za>
In-reply-to
Content 
As long as we are restricted by backwards compatibility, it will be hard to find a hack-free solution. The ideal solution IMO is to re-create _warnings.filters from scratch when _warnings is reloaded, but such a change would be safer only for 3.7.

So I am happy to leave things as they are. At least until something upsets things again :)
History
Date User Action Args
2016-11-22 01:00:20martin.pantersetrecipients: + martin.panter, vstinner, python-dev, serhiy.storchaka, xiang.zhang
2016-11-22 01:00:20martin.pantersetmessageid: <1479776420.2.0.758218535429.issue28688@psf.upfronthosting.co.za>
2016-11-22 01:00:20martin.panterlinkissue28688 messages
2016-11-22 01:00:20martin.pantercreate