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
Having pybind11 keep its own internal thread state can lead to an
inconsistent situation where the Python interpreter has a thread
state but pybind does not, and then when gil_scoped_acquire is
called, pybind creates a new thread state instead of using the one
created by the Python interpreter. This change gets rid of pybind's
internal thread state and always uses the one created by the Python
interpreter.
0 commit comments