[docs] [issue33932] Calling Py_Initialize() twice now triggers a fatal error (Python 3.7)
report at bugs.python.org
Thu Jun 28 08:42:02 EDT 2018
STINNER Victor <vstinner at redhat.com> added the comment:
I reopen the issue because fontforge still fails on Python 3.7.0 final. fontforge calls Py_Initialize() and then calls Py_Main() which fails with an assertion: https://bugzilla.redhat.com/show_bug.cgi?id=1595421
The same code works well on Python 3.6, so should we define this issue as a regression?
* _Py_InitializeCore() which fails
The problem is that the first call of Py_Initialize() sets a first configuration, but then Py_Main() sets a different configuration.
Is it correct to call Py_Initialize() before Py_Main()?
resolution: fixed ->
status: closed -> open
Python tracker <report at bugs.python.org>
More information about the docs