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
Both #123488 and #123134 have made it clear that PEP-684 and multithreading from C haven't been documented properly. In both issues, the following line was misinterpreted:
Python supports the creation of additional interpreters (using Py_NewInterpreter()), but mixing multiple interpreters and the PyGILState_* API is unsupported.
This has been interpreted as "it's safe to call Py_NewInterpreter (or Py_NewInterpreterFromConfig) without the GIL," which it definitely is not! It's just that we can't switch interpreters via PyGILState_* -- that should be clarified.
Uh oh!
There was an error while loading. Please reload this page.
Documentation
Both #123488 and #123134 have made it clear that PEP-684 and multithreading from C haven't been documented properly. In both issues, the following line was misinterpreted:
This has been interpreted as "it's safe to call
Py_NewInterpreter
(orPy_NewInterpreterFromConfig
) without the GIL," which it definitely is not! It's just that we can't switch interpreters viaPyGILState_*
-- that should be clarified.(@encukou, this needs
topic-subinterpreters
)Linked PRs
PyGILState*
for subinterpreters #123728The text was updated successfully, but these errors were encountered: