Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

what does it take for PyCall.jl to drop GIL #1046

Closed
Moelf opened this issue Jul 25, 2023 · 2 comments
Closed

what does it take for PyCall.jl to drop GIL #1046

Moelf opened this issue Jul 25, 2023 · 2 comments

Comments

@Moelf
Copy link

Moelf commented Jul 25, 2023

Numba has a nogil annotation, I'm wondering if we can somehow drop the GIL and what would that imply.

see: JuliaPy/pyjulia#535

@Moelf Moelf closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2023
@Moelf Moelf changed the title what does it take for PyCall.jl to drop GIL? what does it take for PyCall.jl to drop GIL Jul 25, 2023
@Moelf Moelf reopened this Aug 23, 2023
@Moelf Moelf closed this as not planned Won't fix, can't repro, duplicate, stale Aug 23, 2023
@stevengj
Copy link
Member

stevengj commented Aug 23, 2023

See also #882 and JuliaPy/PythonCall.jl#108

@PallHaraldsson
Copy link
Contributor

PallHaraldsson commented Aug 29, 2023

In case relevant, new in 3.12rc1:
https://peps.python.org/pep-0684/

PEP 684: A Per-Interpreter GIL
Sub-interpreters may now be created with a unique GIL per interpreter. This allows Python programs to take full advantage of multiple CPU cores.

EDIT: Moved long text here to: JuliaPy/PythonCall.jl#343

I noticed "closed this as not planned" so discussion likely relevant at PythonCall (not here to not split the discussion), if at all, in case something needs implementing.

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

No branches or pull requests

3 participants