gh-144277: Fix usage of free-threaded terminology in the documentation #144333
+19
−12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ZeroIntensity
requested review from
corona10 and
erlend-aasland
as code owners
vstinner
approved these changes
Jan 30, 2026
Member
vstinner
left a comment
vstinner
left a comment
There was a problem hiding this comment.
LGTM. I like the addition of "free-threaded build" to the Glossary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the discussion in the issue, the correct term for a build configured with
--disable-gilis "free-threaded build" or "free-threading build" (with the hyphen). To ensure we get this right more often, this adds a glossary term for it.I didn't bother updating past news entries here; if someone wants me to do that, let me know!
📚 Documentation preview 📚: https://cpython-previews--144333.org.readthedocs.build/