bpo-33932: Calling Py_Initialize() twice does nothing by vstinner · Pull Request #7845 · python/cpython

@vstinner

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

@vstinner

Exit early if Python is already initialized. Revert my previous
change in _Py_InitializeCore().

zhangyangyu

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>

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>