This repository has been archived by the owner on Aug 10, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 137
Py_NewInterpreter #23
Comments
Both behave and answer to different use case. The downside of NewInterpreter is that you won't share state between the different modules you're running in each interpreters. Also This repo is no longer in an active development state but we gladly accept PR if you open one to add support to the NewInterpreter functions ! |
Closing this issue for now, but feel free to reopen it or a new one if needed. |
Hey, @marcofiocco did you ever tried calling Py_NewInterpreter using the C-API? |
@SagiMedina have you seen this? |
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What do you think about adding support for Py_NewInterpreter and Py_EndInterpreter?
Would this be easier to use rather than using LockOSThread and PyGILState_Ensure?
I'm having issues with the latter, cannot make it work.
The text was updated successfully, but these errors were encountered: