gh-91985: Ensure the same path calculations when repeated with PYTHONHOME #93512
+136
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When an embedded Python is initialized multiple times, getpath.py requires
home
with the same value, for the consistent path configuration.Roughly, the transition of
home
(PyInterpreterState.config.home
) is as below:home
=config.home
(original, local) or_Py_path_config.home
(global)home
,paths
=getpath(home, PYTHONHOME, *._pth)
_Py_path_config.home
=home
(the originalconfig.home
is left as-is)1st initialization with PYTHONHOME:
home
getsNULL
.None
ashome
and returns the value ofPYTHONHOME
.2nd:
home
starts withPYTHONHOME
from_Py_path_config.home
.home
unchanged. The returnedpaths
, which are less flexible than 1st, can cause import errors.In this cycle, the value from
_Py_path_config.home
at step1 needs to be discarded unless the global value was set byPy_SetPythonHome()
.#91985