I’m looking into running python from my audio plugin right now, and there seem to be many viable options.
But from what it seems, python is not designed to run independent interpreters within the same process, which could cause problems if a host uses python as well (or starts doing so in the future).
Bundling my own interpreter or using subinterpreters still seems to share some global state and the global interpreter lock is working per-process.
Is there any way to avoid the annoyance of creating a new process and handling IPC when running Python code in an audio plugin?
The best solution right now seems to be running a local API with flask in another process and calling its endpoints from JUCE (from this post).
If anybody is doing something similar in production, hit me up!