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 Arfrever, Drekin, Gregory.Salvan, barry, dstufft, eric.snow, jcea, ncoghlan, sbspider, serhiy.storchaka, terry.reedy, twouters, vstinner
Date 2017-11-05.04:37:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Bug report (since resolved) that highlighted our general lack of test coverage for the interactions between environment variable based configuration and command line based configuration:

This work revealed the absence, since the refactoring changes the order in which we check environment variables and the command line (we used to check the command line first, and then env vars later during Py_Initialize, now we check env vars in _Py_InitializeCore, and the command line afterwards).

Something I'd also forgotten is that I'd switched the PEP to use "_Py_InitializeRuntime" and "_Py_ConfigureMainInterpreter", but the draft implementation is currently still using "_Py_InitializeCore" and "_Py_InitializeMainInterpreter".

For that last point, it's probably easier to change the PEP back than it is to tinker with the implementation - those specific API names are pretty arbitrary anyway.
Date User Action Args
2017-11-05 04:37:10ncoghlansetrecipients: + ncoghlan, twouters, barry, terry.reedy, jcea, vstinner, Arfrever, eric.snow, serhiy.storchaka, Drekin, dstufft, Gregory.Salvan, sbspider
2017-11-05 04:37:09ncoghlansetmessageid: <>
2017-11-05 04:37:09ncoghlanlinkissue22257 messages
2017-11-05 04:37:08ncoghlancreate