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 docs@python, emilyemorehouse, eric.snow, hroncok, miss-islington, ncoghlan, ned.deily, vstinner, xiang.zhang
Date 2018-06-30.07:17:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530343034.83.0.56676864532.issue33932@psf.upfronthosting.co.za>
In-reply-to
Content
Answering Eric's question about the flag variables though:

* pymain_get_global_config copies the global variable flags to their respective struct entries
* pymain_set_global_config copies the various struct entries to their respective global variable flags

One of the first things that Py_Main() does in 3.7 is to:

- read the global variable flags into the relevant structs
- update the structs based on the CLI options
- write the struct values back to the global flags

This mostly fakes the 3.6-and-earlier behaviour of using the global variables directly.

For anything listed in https://docs.python.org/3/c-api/init.html#global-configuration-variables, we also mostly left any code reading the global variable directly alone, since they're considered a public API for embedding applications to dynamically adjust behaviour and we don't have a good way of deprecating using them for that purpose :(
History
Date User Action Args
2018-06-30 07:17:14ncoghlansetrecipients: + ncoghlan, vstinner, ned.deily, docs@python, eric.snow, xiang.zhang, emilyemorehouse, hroncok, miss-islington
2018-06-30 07:17:14ncoghlansetmessageid: <1530343034.83.0.56676864532.issue33932@psf.upfronthosting.co.za>
2018-06-30 07:17:14ncoghlanlinkissue33932 messages
2018-06-30 07:17:14ncoghlancreate