Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.1k
bpo-34523: Use _PyCoreConfig instead of globals#9005
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Get configuratiom the core configuration of the interpreter, ratherthan getting global configuration variables. For example, replacePy_QuietFlag with core_config->quiet.
bmwiedemann commentedSep 27, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Unfortunately, the description does not tell much about "Why this is good?" (edit: link went to different PR) |
For the long term, I plan to deprecate global variables, especially global configuration variables like Py_QuietFlag. Moreover, I would like to support running two Python interpreters inside the same process but with two different configurations. Seehttps://www.python.org/dev/peps/pep-0554/ for more information about Eric Snow's project@ericsnowcurrently. |
Uh oh!
There was an error while loading.Please reload this page.
Get configuratiom the core configuration of the interpreter, rather
than getting global configuration variables. For example, replace
Py_QuietFlag with core_config->quiet.
https://bugs.python.org/issue34523