STINNER Victor <vstin...@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? Call stack: * Py_Main() * pymain_main() * _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 <rep...@bugs.python.org> <https://bugs.python.org/issue33932> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
