You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
I'm not an expert on the GIL / Python C api, but the documentation suggests that every single API call needs to be executed within the context of a held GIL lock: "... only the thread that has acquired the GIL may operate on Python objects or call Python/C API functions."
I've noticed a few places where the GIL isn't being acquired: Java_org_jpy_PyLib_newDict and Java_org_jpy_PyLib_copyDict (a non-exhaustive search). Should these places acquire the GIL?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not an expert on the GIL / Python C api, but the documentation suggests that every single API call needs to be executed within the context of a held GIL lock: "... only the thread that has acquired the GIL may operate on Python objects or call Python/C API functions."
I've noticed a few places where the GIL isn't being acquired:
Java_org_jpy_PyLib_newDict
andJava_org_jpy_PyLib_copyDict
(a non-exhaustive search). Should these places acquire the GIL?The text was updated successfully, but these errors were encountered: