Use _PyCoreConfig rather than global configuration variables

[vstinner]

BPO	36900
Nosy	@vstinner
PRs	bpo-36900: import.c uses PyInterpreterState.core_config #13278 bpo-36900: Replace global conf vars with config #13299 bpo-36900: Fix compilation on HP-UX #13614

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2019-05-14.15:35:57.545>
created_at = <Date 2019-05-13.11:07:28.616>
labels = ['interpreter-core', '3.8']
title = 'Use _PyCoreConfig rather than global configuration variables'
updated_at = <Date 2019-05-28.10:24:04.155>
user = 'https://github.com/vstinner'

bugs.python.org fields:

activity = <Date 2019-05-28.10:24:04.155>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2019-05-14.15:35:57.545>
closer = 'vstinner'
components = ['Interpreter Core']
creation = <Date 2019-05-13.11:07:28.616>
creator = 'vstinner'
dependencies = []
files = []
hgrepos = []
issue_num = 36900
keywords = ['patch']
message_count = 6.0
messages = ['342310', '342338', '342398', '342478', '342479', '343760']
nosy_count = 1.0
nosy_names = ['vstinner']
pr_nums = ['13278', '13299', '13614']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue36900'
versions = ['Python 3.8']

[vstinner]

PyInterpreterState.config is now preferred over global configuration variables, so two interpreters can have a different configuration, the "state" of an interpreter is now better defined (especially when and how its configuration is set).

Attached PRs fix these isssues.

[vstinner]

New changeset 410b85a7f701be280eb15b0ca4fe116e86f1d008 by Victor Stinner in branch 'master':
bpo-36900: import.c uses PyInterpreterState.core_config (GH-13278)
https://github.com/python/cpython/commit/410b85a7f701be280eb15b0ca4fe116e86f1d008

[vstinner]

With PR 13299, most global variable configurables are not directly accessed, outside code to initialize _PyPreConfig and _PyCoreConfig.

parser.c: Py_DebugFlag
fileutils.c: Py_UTF8Mode, Py_LegacyWindowsFSEncodingFlag
frozenmain.c: Py_VerboseFlag
Py_FdIsInteractive(): Py_InteractiveFlag
PySys_SetArgv(): Py_IsolatedFlag()
Py_GETENV(): Py_IsolatedFlag

The problem is that these files, functions and macros may be used before Python is initialized: before Python has an interpreter.

[vstinner]

New changeset c96be811fa7da8ddcea18cc7abcae94e0f5ff966 by Victor Stinner in branch 'master':
bpo-36900: Replace global conf vars with config (GH-13299)
https://github.com/python/cpython/commit/c96be811fa7da8ddcea18cc7abcae94e0f5ff966

[vstinner]

There are a few remaining usage of these global configuration variables, but it will be tricky to remove them:
https://bugs.python.org/issue36900#msg342398

I consider that I'm done on this topic, so I close the issue.

[vstinner]

New changeset 9ea277a788eabec102e8fe613b7f1e27995d5918 by Victor Stinner in branch 'master':
bpo-36900: Fix compilation on HP-UX (GH-13614)
https://github.com/python/cpython/commit/9ea277a788eabec102e8fe613b7f1e27995d5918