@@ -82,9 +82,10 @@ and improvements in user-friendliness and correctness.
82
82
83
83
.. PEP-sized items next.
84
84
85
+ * :ref: `PEP 779: Free-threaded Python is officially supported <whatsnew314-pep779 >`
85
86
* :ref: `PEP 649 and 749: deferred evaluation of annotations <whatsnew314-pep649 >`
86
- * :ref: `PEP 734: Multiple Interpreters in the Stdlib <whatsnew314-pep734 >`
87
- * :ref: `PEP 741: Python Configuration C API <whatsnew314-pep741 >`
87
+ * :ref: `PEP 734: Multiple interpreters in the stdlib <whatsnew314-pep734 >`
88
+ * :ref: `PEP 741: Python configuration C API <whatsnew314-pep741 >`
88
89
* :ref: `PEP 750: Template strings <whatsnew314-pep750 >`
89
90
* :ref: `PEP 758: Allow except and except* expressions without parentheses <whatsnew314-pep758 >`
90
91
* :ref: `PEP 761: Discontinuation of PGP signatures <whatsnew314-pep761 >`
@@ -124,9 +125,35 @@ of Python. See :ref:`below <whatsnew314-refcount>` for details.
124
125
New features
125
126
============
126
127
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
+
127
154
.. _whatsnew314-pep734 :
128
155
129
- PEP 734: Multiple Interpreters in the Stdlib
156
+ PEP 734: Multiple interpreters in the stdlib
130
157
--------------------------------------------
131
158
132
159
The CPython runtime supports running multiple copies of Python in the
@@ -392,7 +419,7 @@ As can be seen, the API is similar to the APIs of the :mod:`!lzma` and
392
419
:mod: `!bz2 ` modules.
393
420
394
421
(Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun,
395
- Victor Stinner, and Rogdham in :gh: `132983 `)
422
+ Victor Stinner, and Rogdham in :gh: `132983 `. )
396
423
397
424
.. seealso ::
398
425
:pep: `784 `.
@@ -727,7 +754,7 @@ Improved error messages
727
754
728
755
.. _whatsnew314-pep741 :
729
756
730
- PEP 741: Python Configuration C API
757
+ PEP 741: Python configuration C API
731
758
-----------------------------------
732
759
733
760
Add a :ref: `PyInitConfig C API <pyinitconfig_api >` to configure the Python
@@ -1266,7 +1293,7 @@ configparser
1266
1293
to :meth: `configparser.ConfigParser.write ` keys containing delimiters or
1267
1294
beginning with the section header pattern will raise a
1268
1295
:class: `configparser.InvalidWriteError `.
1269
- (Contributed by Jacob Lincoln in :gh: `129270 `)
1296
+ (Contributed by Jacob Lincoln in :gh: `129270 `. )
1270
1297
1271
1298
contextvars
1272
1299
-----------
@@ -2755,8 +2782,8 @@ New features
2755
2782
2756
2783
* Add :c:func: `PyType_GetBaseByToken ` and :c:data: `Py_tp_token ` slot for easier
2757
2784
superclass identification, which attempts to resolve the `type checking issue
2758
- <https://peps.python.org/pep-0630/#type-checking> `__ mentioned in :pep: `630 `
2759
- (:gh: `124153 `).
2785
+ <https://peps.python.org/pep-0630/#type-checking> `__ mentioned in :pep: `630 `.
2786
+ (Contributed in :gh: `124153 `.)
2760
2787
2761
2788
* Add :c:func: `PyUnicode_Equal ` function to the limited C API:
2762
2789
test if two strings are equal.
0 commit comments