[issue35388] _PyRuntime_Initialize() called after Py_Finalize() does nothing

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35388] _PyRuntime_Initialize() called after Py_Finalize() does nothing

STINNER Victor added the comment: New changeset fd23cfa464ab93273370475900819c1ea37c852f by Victor Stinner in branch 'master': bpo-35388: Fix _PyRuntime_Finalize() (GH-12443) https://github.com/python/cpython/commit/fd23cfa464ab93273370475900819c1ea37c852f --

[issue35388] _PyRuntime_Initialize() called after Py_Finalize() does nothing

STINNER Victor added the comment: PR 12443 fix the issue. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35388] _PyRuntime_Initialize() called after Py_Finalize() does nothing

Change by STINNER Victor : -- keywords: +patch pull_requests: +12398 stage: -> patch review ___ Python tracker ___ ___

[issue35388] _PyRuntime_Initialize() called after Py_Finalize() does nothing

New submission from STINNER Victor : When Python is embedded, it should be possible to call the following Python function multiple times: void func(void) { Py_Initialize(); /* do something in Python */ Py_Finalize(); } Py_Finalize() ends by calling _PyRuntime_Finalize(). Problem: when