8000 acquire GIL by default when making PyObject calls · Issue #285 · pythonnet/pythonnet · GitHub
[go: up one dir, main page]
Skip to content

acquire GIL by default when making PyObject calls #285

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.

Sign up for GitHub

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

Jump to bottom
Closed
den-run-ai opened this issue Nov 7, 2016 · 2 comments
Closed

acquire GIL by default when making PyObject calls #285

den-run-ai opened this issue Nov 7, 2016 · 2 comments
Assignees
@den-run-ai

Comments

@den-run-ai
Copy link
Contributor

Right now the GIL has to be acquired for each call to PyObject functions or methods. Maybe these should be with GIL acquired by default? We can include context manager to force releasing of GIL by explicit request.
@den-run-ai
Copy link
Contributor Author

here is how this was done by @matthid in F#:

https://yaaf.de/blog/post/2016-05-28/Having%20Fun%20with%20Computation%20Expressions

@den-run-ai den-run-ai self-assigned this Jan 24, 2017
@den-run-ai den-run-ai added this to the 2.3.0 milestone Feb 2, 2017
@yagweb yagweb mentioned this issue Feb 23, 2017
Merged
@vmuriart vmuriart modified the milestones: 2.4.0, 2.3.0 Mar 10, 2017
@filmor
Copy link
Member
filmor commented Jul 11, 2017

Can you give an example? Do you think this is actually feasible for the next release? If not, please remove the milestone.

@filmor filmor modified the milestones: 2.4.0, 3.0.0 Aug 30, 2018
@lostmsu lostmsu removed this from the 3.0.0 milestone Sep 24, 2021
@filmor filmor closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@den-run-ai den-run-ai

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@filmor @lostmsu @den-run-ai @vmuriart
0