Skip to content

gh-123672: Clarify the usage of PyGILState* for subinterpreters #123728

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

Closed
ZeroIntensity wants to merge 23 commits into from
Closed

gh-123672: Clarify the usage of PyGILState* for subinterpreters #123728

Changes from 4 commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
3782e3a
Clarify the usage of PyGILState* for subinterpreters.
ZeroIntensity Sep 5, 2024
77df9e7
Add extra sentence
ZeroIntensity Sep 5, 2024
bd2681f
Switch to Sphinx type instead of expr
ZeroIntensity Sep 5, 2024
858c499
Fix italics.
ZeroIntensity Sep 5, 2024
eb56367
Update Doc/c-api/init.rst
ZeroIntensity Sep 5, 2024
40dbd18
Fix typo.
ZeroIntensity Sep 5, 2024
eedefd8
Update init.rst
ZeroIntensity Sep 5, 2024
58be1c8
Update Doc/c-api/init.rst
ZeroIntensity Sep 6, 2024
76d90d8
Clarify usage of what interpreter you end up in with PyGILState_Ensure
ZeroIntensity Sep 7, 2024
e7be1ad
More clarification.
ZeroIntensity Sep 7, 2024
adbef3a
Update Doc/c-api/init.rst
ZeroIntensity Sep 7, 2024
46060a7
Clarify the phrase 'current thread'
ZeroIntensity Sep 7, 2024
f1442ab
Fix merge conflicts.
ZeroIntensity Sep 7, 2024
426cb07
Fix typo.
ZeroIntensity Sep 7, 2024
a83eab2
Clarify what PyGILState_Ensure() does for a sub-interpreter
ZeroIntensity Sep 7, 2024
6036f65
Add line break.
ZeroIntensity Sep 7, 2024
383dfe1
Fix merge conflicts.
ZeroIntensity Sep 7, 2024
edfd150
Update init.rst
ZeroIntensity Sep 8, 2024
f24b571
Update init.rst
ZeroIntensity Sep 8, 2024
93d90ad
Update init.rst
ZeroIntensity Sep 8, 2024
cbbe235
Swap Py_EndInterpreter and PyGILState_Release
ZeroIntensity Sep 8, 2024
a432e77
Update init.rst
ZeroIntensity Sep 9, 2024
f11b7fc
Remove excerpt from `PyGILState_Ensure` and shorten wording
ZeroIntensity Sep 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions Doc/c-api/init.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -919,8 +919,11 @@ from a C thread is::
Note that the ``PyGILState_*`` functions assume there is only one global
interpreter (created automatically by :c:func:`Py_Initialize`). Python
supports the creation of additional interpreters (using
:c:func:`Py_NewInterpreter`), but mixing multiple interpreters and the
``PyGILState_*`` API is unsupported.
:c:func:`Py_NewInterpreter`), but switching between interpreters via the
``PyGILState_*`` API is unsupported. With that being said, you still need
to hold the :term:`GIL` in order to *create* a subinterpreter, even if using
a per-interpreter GIL (see :pep:`684`). The need for :c:type:`PyGILState_STATE`
doesn't go away when creating isolated subinterpreters!
Comment thread
ZeroIntensity marked this conversation as resolved.
Resolved


.. _fork-and-threads:
Expand Down