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 eric.snow
Recipients brett.cannon, eric.snow, steve.dower
Date 2019-04-26.22:28:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
(See Include/internal/pycore_warnings.h and Python/_warnings.c.)

The warnings module's state (filters, default action, etc.) is currently stored at the level of the global runtime.  That's a problem for the following reasons:

* Python objects are getting stored in _PyRuntimeState
* it breaks the isolation of behavior between interpreters
* objects are leaking between interpreters
* importing the module in a subinterpreter effectively resets the module's state

While those are all a problem in a future where interpreters don't share the GIL, that last one is a problem right now for people using subinterpreters.

One of the following should happen:

* move warnings state down to PyInterpreterState
* move warnings state into PyInterpreterState.dict
* use the module-state API (PEP 3121)
* just work out of the module's __dict__

I could also see use cases for *also* configuring warnings process-wide but that could be handled separately if actually desired.
Date User Action Args
2019-04-26 22:28:58eric.snowsetrecipients: + eric.snow, brett.cannon, steve.dower
2019-04-26 22:28:58eric.snowsetmessageid: <>
2019-04-26 22:28:58eric.snowlinkissue36737 messages
2019-04-26 22:28:57eric.snowcreate