From aba80fa4ba9849aed3d61bf3a5055801dc8c17b0 Mon Sep 17 00:00:00 2001 From: sobolevn Date: Mon, 8 Sep 2025 16:44:44 +0300 Subject: [PATCH] gh-138644: Update c-api docs of `PyInterpreterState` about PEP-684 (GH-138651) (cherry picked from commit 4f0c267b40e52b83b2e1515aa0dd74eda31ae18a) Co-authored-by: sobolevn Co-authored-by: Peter Bierma --- Doc/c-api/init.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst index d34502f50b53dd..6a272a4f5fcb87 100644 --- a/Doc/c-api/init.rst +++ b/Doc/c-api/init.rst @@ -1184,6 +1184,12 @@ code, or when embedding the Python interpreter: interpreter lock is also shared by all threads, regardless of to which interpreter they belong. + .. versionchanged:: 3.12 + + :pep:`684` introduced the possibility + of a :ref:`per-interpreter GIL `. + See :c:func:`Py_NewInterpreterFromConfig`. + .. c:type:: PyThreadState @@ -1875,6 +1881,8 @@ function. You can create and destroy them using the following functions: haven't been explicitly destroyed at that point. +.. _per-interpreter-gil: + A Per-Interpreter GIL --------------------- @@ -1886,7 +1894,7 @@ being blocked by other interpreters or blocking any others. Thus a single Python process can truly take advantage of multiple CPU cores when running Python code. The isolation also encourages a different approach to concurrency than that of just using threads. -(See :pep:`554`.) +(See :pep:`554` and :pep:`684`.) Using an isolated interpreter requires vigilance in preserving that isolation. That especially means not sharing any objects or mutable