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 ncoghlan
Recipients emilyemorehouse, eric.snow, hroncok, ncoghlan, vstinner
Date 2018-06-30.10:47:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yeah, I've asked Miro to try essentially that in

My concern is that Py_Main used to keep a *lot* of state on the local C stack that we've now moved into the main interpreter config.

So my suspicion is that even that change I've asked Miro to try may not do the right thing, but it really depends on *why* fontforge is calling Py_Main, and what they're passing in argc and argv.

Given that the embedded Py_Initialize is a no-op, they may be better off just copying out the parts they actually need from the code execution aspects of it, and skipping the Py_Main call entirely.
Date User Action Args
2018-06-30 10:47:28ncoghlansetrecipients: + ncoghlan, vstinner, eric.snow, emilyemorehouse, hroncok
2018-06-30 10:47:28ncoghlansetmessageid: <>
2018-06-30 10:47:28ncoghlanlinkissue34008 messages
2018-06-30 10:47:28ncoghlancreate