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, ncoghlan, ronaldoussoren, vstinner
Date 2018-07-28.03:56:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532750199.18.0.56676864532.issue34247@psf.upfronthosting.co.za>
In-reply-to
Content
Comparing to Python 3.6, we can see that the code to update the C global flags from the environment variables used to live directly in _PyInitializeEx_Private: https://github.com/python/cpython/blob/9d85856044a2c7d681ea38b5ff99af375b228a0f/Python/pylifecycle.c#L305

In Python 3.7 that section (https://github.com/python/cpython/blob/3.7/Python/pylifecycle.c#L913 ) currently calls _PyCoreConfig_Read instead, which *only* updates the config struct - it doesn't update the C level global variables.

By contrast, Py_Main eventually calls https://github.com/python/cpython/blob/7cbde0e09daba4259565738e48f141851287fe29/Modules/main.c#L1394 which handles writing the state from the config struct back to the global variables.
History
Date User Action Args
2018-07-28 03:56:39ncoghlansetrecipients: + ncoghlan, brett.cannon, ronaldoussoren, vstinner, eric.snow
2018-07-28 03:56:39ncoghlansetmessageid: <1532750199.18.0.56676864532.issue34247@psf.upfronthosting.co.za>
2018-07-28 03:56:39ncoghlanlinkissue34247 messages
2018-07-28 03:56:38ncoghlancreate