Skip to content

Commit bb657b2

Browse files
Fix outdated wording (#137232)
1 parent 48f8831 commit bb657b2

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

Doc/howto/free-threading-python.rst

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -120,9 +120,8 @@ objects of these types may see increased memory usage. This is expected to be
120120
addressed in the 3.14 release.
121121

122122
Additionally, numeric and string literals in the code as well as strings
123-
returned by :func:`sys.intern` are also immortalized. This behavior is
124-
expected to remain in the 3.14 free-threaded build.
125-
123+
returned by :func:`sys.intern` are also immortalized. This behavior is retained
124+
in the 3.14 free-threaded build.
126125

127126
Frame objects
128127
-------------
@@ -150,8 +149,8 @@ compared to the default GIL-enabled build. In 3.13, this overhead is about
150149
40% on the `pyperformance <https://pyperformance.readthedocs.io/>`_ suite.
151150
Programs that spend most of their time in C extensions or I/O will see
152151
less of an impact. The largest impact is because the specializing adaptive
153-
interpreter (:pep:`659`) is disabled in the free-threaded build. We expect
154-
to re-enable it in a thread-safe way in the 3.14 release. This overhead is
152+
interpreter (:pep:`659`) is disabled in the free-threaded build. We
153+
re-enabled it in a thread-safe way in the 3.14 release. This overhead is
155154
expected to be reduced in upcoming Python release. We are aiming for an
156155
overhead of 10% or less on the pyperformance suite compared to the default
157156
GIL-enabled build.

0 commit comments

Comments
 (0)