Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-33932: Calling Py_Initialize() twice does nothing #7845

Merged
merged 2 commits into from
Jun 22, 2018
Merged

bpo-33932: Calling Py_Initialize() twice does nothing #7845

merged 2 commits into from
Jun 22, 2018

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Jun 21, 2018

Calling Py_Initialize() twice does nothing, instead of failing with a
fatal error: restore the Python 3.6 behaviour.

https://bugs.python.org/issue33932

Calling Py_Initialize() twice does nothing, instead of failing with a
fatal error: restore the Python 3.6 behaviour.
Exit early if Python is already initialized. Revert my previous
change in _Py_InitializeCore().
@vstinner
Copy link
Member Author

Oops, I didn't ran the test before pushing. Shame on my. It should be better with the second commit :-)

@vstinner
Copy link
Member Author

@serhiy-storchaka: Would you mind to have a look at this change? It seems to fix a regression introduced in Python 3.7: https://bugs.python.org/issue33932

I'm not sure that it has been made on purpose. At least, it broke an application in the wild...

@miss-islington
Copy link
Contributor

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

@bedevere-bot
Copy link

GH-7859 is a backport of this pull request to the 3.7 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jun 22, 2018
Calling Py_Initialize() twice does nothing, instead of failing with a
fatal error: restore the Python 3.6 behaviour.
(cherry picked from commit 209abf7)

Co-authored-by: Victor Stinner <vstinner@redhat.com>
@vstinner vstinner deleted the py_init branch June 22, 2018 17:26
miss-islington added a commit that referenced this pull request Jun 22, 2018
Calling Py_Initialize() twice does nothing, instead of failing with a
fatal error: restore the Python 3.6 behaviour.
(cherry picked from commit 209abf7)

Co-authored-by: Victor Stinner <vstinner@redhat.com>
ned-deily pushed a commit to ned-deily/cpython that referenced this pull request Jun 27, 2018
Calling Py_Initialize() twice does nothing, instead of failing with a
fatal error: restore the Python 3.6 behaviour.
(cherry picked from commit 209abf7)

Co-authored-by: Victor Stinner <vstinner@redhat.com>
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.

6 participants