Martin Panter added the comment: 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 :) ---------- resolution: -> out of date stage: -> resolved status: open -> closed superseder: -> Warning -- warnings.filters was modified by test_warnings _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28688> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
