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
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().
|
Oops, I didn't ran the test before pushing. Shame on my. It should be better with the second commit :-) |
|
@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... |
|
Thanks @vstinner for the PR |
|
GH-7859 is a backport of this pull request to the 3.7 branch. |
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>
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>
Calling Py_Initialize() twice does nothing, instead of failing with a fatal error: restore the Python 3.6 behaviour.
Calling Py_Initialize() twice does nothing, instead of failing with a fatal error: restore the Python 3.6 behaviour.
Calling Py_Initialize() twice does nothing, instead of failing with a
fatal error: restore the Python 3.6 behaviour.
https://bugs.python.org/issue33932