This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients emilyemorehouse, eric.snow, hroncok, ncoghlan, vstinner
Date 2018-06-30.10:21:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CA+3bQGH_g9w4A=-yf0nn8ub5qPHBm34s9-3ehpQequYZ9DTBhA@mail.gmail.com>
In-reply-to <1530342370.21.0.56676864532.issue34008@psf.upfronthosting.co.za>
Content
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.
History
Date User Action Args
2018-06-30 10:21:46vstinnersetrecipients: + vstinner, ncoghlan, eric.snow, emilyemorehouse, hroncok
2018-06-30 10:21:46vstinnerlinkissue34008 messages
2018-06-30 10:21:46vstinnercreate