STINNER Victor added the comment: I'm ok to close this bug :-)
> 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. Currently it's not possible to "reload" the _warnings module since it doesn't use the "module state" API. I don't see how you want to trigger an action in the _warnings module itself when it is "reloaded". Filteres are used internally in the _warnings C module. Maybe we need to enhance the _warnings C module to use the "module state" API? (Is it the PEP 489?) ---------- _______________________________________ 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
