➜

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 vstinner
Recipients martin.panter, python-dev, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-11-22.08:47:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYXPxja83qWepCKwVye=_pfnzQXhvYXOXTnAseQAtcV9A@mail.gmail.com>
In-reply-to <1479776450.52.0.0197677353587.issue28688@psf.upfronthosting.co.za>
Content 
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?)
History
Date User Action Args
2016-11-22 08:47:16vstinnersetrecipients: + vstinner, python-dev, martin.panter, serhiy.storchaka, xiang.zhang
2016-11-22 08:47:16vstinnerlinkissue28688 messages
2016-11-22 08:47:15vstinnercreate