Skip to content
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.

Py_NewInterpreter #23

Closed
marcofiocco opened this issue Dec 16, 2019 · 5 comments
Closed

Py_NewInterpreter #23

marcofiocco opened this issue Dec 16, 2019 · 5 comments

Comments

@marcofiocco
Copy link

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.

@hush-hush
Copy link
Member

hush-hush commented Dec 17, 2019

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 PyGILState_Ensure will still be needed when extending Python with custom C/CGO module.

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 !

@hush-hush
Copy link
Member

Closing this issue for now, but feel free to reopen it or a new one if needed.

@SagiMedina
Copy link

SagiMedina commented Dec 13, 2020

Hey, @marcofiocco did you ever tried calling Py_NewInterpreter using the C-API?
If so, care to share the experience?

@christian-korneck
Copy link
Contributor

@SagiMedina have you seen this?

@SagiMedina
Copy link

@SagiMedina have you seen this?

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants