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

Make sure detail::get_internals acquires the GIL before making Python calls #1836

Merged
merged 1 commit into from
Jul 15, 2019

Conversation

saran-t
Copy link
Contributor

@saran-t saran-t commented Jul 11, 2019

This is only necessary if get_internals is called for the first time in a given module when the running thread is in a GIL-released state.

Fixes #1364

@saran-t saran-t force-pushed the get_internals_gil branch 2 times, most recently from 720465a to e553bce Compare July 11, 2019 18:43
…on calls.

This is only necessary if `get_internals` is called for the first time in a given module when the running thread is in a GIL-released state.

Fixes pybind#1364
@wjakob
Copy link
Member

wjakob commented Jul 15, 2019

closed following #1364.

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

Successfully merging this pull request may close these issues.

gil_scoped_acquire can make unsafe CPython calls without holding the GIL
2 participants