@@ -82,6 +82,7 @@ and improvements in user-friendliness and correctness.
8282
8383.. PEP-sized items next.
8484
85+ * :ref: `PEP 779: Free-threaded Python is officially supported <whatsnew314-pep779 >`
8586* :ref: `PEP 649 and 749: deferred evaluation of annotations <whatsnew314-pep649 >`
8687* :ref: `PEP 734: Multiple interpreters in the stdlib <whatsnew314-pep734 >`
8788* :ref: `PEP 741: Python configuration C API <whatsnew314-pep741 >`
@@ -124,6 +125,32 @@ of Python. See :ref:`below <whatsnew314-refcount>` for details.
124125New features
125126============
126127
128+ .. _whatsnew314-pep779 :
129+
130+ PEP 779: Free-threaded Python is officially supported
131+ -----------------------------------------------------
132+
133+ The free-threaded build of Python is now supported and no longer experimental.
134+ This is the start of phase II where free-threaded Python is officially supported
135+ but still optional.
136+
137+ We are confident that the project is on the right path, and we appreciate the
138+ continued dedication from everyone working to make free-threading ready for
139+ broader adoption across the Python community.
140+
141+ With these recommendations and the acceptance of this PEP, we as the Python
142+ developer community should broadly advertise that free-threading is a supported
143+ Python build option now and into the future, and that it will not be removed
144+ without a proper deprecation schedule.
145+
146+ Any decision to transition to phase III, with free-threading as the default or
147+ sole build of Python is still undecided, and dependent on many factors both
148+ within CPython itself and the community. This decision is for the future.
149+
150+ .. seealso ::
151+ :pep: `779 ` and its `acceptance
152+ <https://discuss.python.org/t/pep-779-criteria-for-supported-status-for-free-threaded-python/84319/123> `__.
153+
127154.. _whatsnew314-pep734 :
128155
129156PEP 734: Multiple interpreters in the stdlib
0 commit comments