Skip to content

[3.8] bpo-38234: Fix PyConfig_Read() when Py_SetPath() was called (GH-16298)#16313

Merged
vstinner merged 2 commits intopython:3.8from
vstinner:pathconfig38
Sep 21, 2019
Merged

[3.8] bpo-38234: Fix PyConfig_Read() when Py_SetPath() was called (GH-16298)#16313
vstinner merged 2 commits intopython:3.8from
vstinner:pathconfig38

Conversation

@vstinner
Copy link
Copy Markdown
Member

@vstinner vstinner commented Sep 20, 2019

The DLL path is not computed from any user configuration and cannot
be configured by PyConfig. Instead, add a new _Py_dll_path global variable.

Remove _PyConfig_SetPathConfig(): replaced with _PyPathConfig_Init().

Py_Initialize() now longer sets the "global path configuration",
but only initialize _Py_dll_path.

(cherry picked from commit c422167)
* If Py_SetPath() has been called, _PyConfig_InitPathConfig() now
  uses its value.
* Py_Initialize() now longer copies path configuration from PyConfig
  to the global path configuration (_Py_path_config).

(cherry picked from commit e267793)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants