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 shakfu
Recipients christoph.wiedemann, cschramm, eric.snow, ncoghlan, petr.viktorin, scoder, shakfu, vstinner
Date 2021-04-12.02:22:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618194177.59.0.407117836588.issue34309@roundup.psfhosted.org>
In-reply-to
Content
In my project (https://github.com/shakfu/py-js), which provides an embedded python3 interpreter to Max/MSP in the form of an 'external' plugin, I have faced similar issues of being unable to reload extension modules, namely numpy, without reliably crashing the host application, in this case Max. 

Being able to reload extension modules cleanly is absolutely critical especially in case when python is embedded. Since Numpy is one of the key reasons why people would want to use Python, such a constraint, in this embedded context, becomes a sufficient reason not to use Python at all.

For example, I have recently taken note of similar frustration with this exact same issue from the VCV project (https://community.vcvrack.com/t/blowing-the-dust-off-python-in-prototype/12909). I quote: "I should add that CPython and more notably numpy do not support nor advise a complete restart of the interpreter in embedded scenarios without restarting the host process which kind of defeats our purpose in Prototype.
At that point I think I can safely take a step back and turn to the dev community looking for suggestions. Should we throw away numpy, or even python, altogether?"
History
Date User Action Args
2021-04-12 02:22:57shakfusetrecipients: + shakfu, ncoghlan, scoder, vstinner, petr.viktorin, eric.snow, cschramm, christoph.wiedemann
2021-04-12 02:22:57shakfusetmessageid: <1618194177.59.0.407117836588.issue34309@roundup.psfhosted.org>
2021-04-12 02:22:57shakfulinkissue34309 messages
2021-04-12 02:22:57shakfucreate