Skip to content

Commit 494a2ea

Browse files
committed
Docs: drop historical framing from the FAQ's GIL answer
1 parent 9e973db commit 494a2ea

1 file changed

Lines changed: 6 additions & 8 deletions

File tree

‎Doc/faq/library.rst‎

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -421,14 +421,12 @@ deployment on high-end multiprocessor server machines, because a multi-threaded
421421
Python program effectively only uses one CPU, due to the insistence that
422422
(almost) all Python code can only run while the GIL is held.
423423
424-
With the approval of :pep:`703` the GIL can be disabled in CPython. This is
425-
implemented as an optional compile-time flag (:option:`--disable-gil`), so
426-
separate builds are available with and without the GIL. The first release
427-
containing this work was Python 3.13, where it was experimental; the
428-
:term:`free-threaded <free threading>` build is officially supported as of
429-
Python 3.14. See :ref:`freethreading-python-howto` for details. Long-term,
430-
the hope is to settle on a single build, once the performance implications of
431-
removing the GIL are fully understood.
424+
CPython has a supported :term:`free-threaded <free threading>` build in which
425+
the GIL is disabled (:pep:`703`). It is built with the
426+
:option:`--disable-gil` configure option, so separate builds are available with
427+
and without the GIL. See :ref:`freethreading-python-howto` for details.
428+
Long-term, the hope is to settle on a single build, once the performance
429+
implications of removing the GIL are fully understood.
432430
433431
The current work to remove the GIL is based on a
434432
`fork of Python 3.9 with the GIL removed <https://github.com/colesbury/nogil>`_

0 commit comments

Comments
 (0)