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 brett.cannon, eric.snow, miss-islington, ncoghlan, ned.deily, ronaldoussoren, vstinner
Date 2018-09-20.12:32:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The "ill-defined" in Python 3.6 relates to the fact that we never actually defined or tested which environment variables were read by Py_Main and which ones were read by Py_Initialize, since the majority of our tests only covered Py_Main (by launching a full Python subprocess).

Thus the only way to find out which environment variables fell into which category would be to read the Python 3.6 source code.

That's technically still the case for Python 3.7, but Victor's done some excellent refactoring work so it's much clearer in the code which vars may be updated if Py_Initialize is run a second time.
Date User Action Args
2018-09-20 12:32:35ncoghlansetrecipients: + ncoghlan, brett.cannon, ronaldoussoren, vstinner, ned.deily, eric.snow, miss-islington
2018-09-20 12:32:35ncoghlansetmessageid: <>
2018-09-20 12:32:35ncoghlanlinkissue34247 messages
2018-09-20 12:32:35ncoghlancreate