Skip to content

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

Closed
miss-islington wants to merge 1 commit intopython:3.8from
miss-islington:backport-e267793-3.8
Closed

[3.8] bpo-38234: Fix PyConfig_Read() when Py_SetPath() was called (GH-16298)#16312
miss-islington wants to merge 1 commit intopython:3.8from
miss-islington:backport-e267793-3.8

Conversation

@miss-islington
Copy link
Copy Markdown
Contributor

@miss-islington miss-islington commented Sep 20, 2019

  • 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)

Co-authored-by: Victor Stinner [email protected]

https://bugs.python.org/issue38234

…-16298)

* 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)

Co-authored-by: Victor Stinner <[email protected]>
@miss-islington
Copy link
Copy Markdown
Contributor Author

@vstinner: Status check is done, and it's a failure ❌ .

@vstinner
Copy link
Copy Markdown
Member

I wrote PR #16313 instead.

@vstinner vstinner closed this Sep 23, 2019
@miss-islington miss-islington deleted the backport-e267793-3.8 branch September 23, 2019 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants