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 ncoghlan
Recipients eric.snow, htgoebel, ncoghlan, ned.deily, pmpp, springermac, vstinner
Date 2018-03-25.05:48:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I added the new test case, and found to my surprise that it didn't fail, even in debug mode (where there aren't any default filters).

The point I had missed was that even though warnoptions can be NULL in CoreConfig, _Py_MainInterpreterConfig_Read ensures that it's never NULL for the main interpreter config (which is what _PySys_EndInit reads), which means that neither we nor any embedding application can currently trigger the code path in get_warnoptions() that lazily creates the warnings list without adding the reference back into the config settings.

We'll need to fix that before we make the new configuration API public, but for now I'm just going to note it in the source code as a "PEP432 TODO".
Date User Action Args
2018-03-25 05:48:01ncoghlansetrecipients: + ncoghlan, htgoebel, vstinner, ned.deily, pmpp, eric.snow, springermac
2018-03-25 05:48:01ncoghlansetmessageid: <>
2018-03-25 05:48:01ncoghlanlinkissue33042 messages
2018-03-25 05:48:00ncoghlancreate