[issue34008] Do we support calling Py_Main() after Py_Initialize()?

[STINNER Victor]

STINNER Victor <vstinner at redhat.com> added the comment:

Even if it's ugly, calling Py_Main() after Py_Initialize() works in Python
3.6 by ignoring the new config of Py_Main(). I suggest to do nothing (just
return) when Py_Initialize() is called again by Py_Main() in Python 3.7. It
would fix the fontforge *regression*.

I suggest to only enhance the code (really apply the new Py_Main() config)
in the master branch. From what I saw, apply the new config is not trivial.
It will take time to decide what to do for *each* option.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34008>
_______________________________________