Skip to content

docs: revise GIL section for Python 3.13 updates - #742

Merged
dbrattli merged 2 commits into
ReactiveX:masterfrom
timkofu:master
Jul 27, 2026
Merged

docs: revise GIL section for Python 3.13 updates#742
dbrattli merged 2 commits into
ReactiveX:masterfrom
timkofu:master

Conversation

@timkofu

@timkofu timkofu commented Nov 8, 2025

Copy link
Copy Markdown
Contributor

Updated GIL explanation to include changes in Python 3.13 and free-threading mode.

Updated GIL explanation to include changes in Python 3.13 and free-threading mode.
@coveralls

coveralls commented Nov 8, 2025

Copy link
Copy Markdown

Coverage Status

coverage: 93.495%. remained the same — timkofu:master into ReactiveX:master

@dbrattli dbrattli changed the title Revise GIL section for Python 3.13 updates docs: revise GIL section for Python 3.13 updates Jul 27, 2026

@dbrattli dbrattli left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating

@dbrattli
dbrattli merged commit 2271867 into ReactiveX:master Jul 27, 2026
22 checks passed
dbrattli added a commit that referenced this pull request Jul 27, 2026
Follow-up to #742, which updated the GIL section to mention free
threading but stopped one version short and introduced some formatting
noise.

Content:
- Free threading was experimental in 3.13 and became officially
  supported in 3.14 (PEP 779). The previous text presented 3.13 as the
  milestone, which both overstates 3.13 and omits 3.14 -- the version
  this project already tests against.
- Clarify that the free-threaded interpreter is a separate build, not a
  runtime switch on a normal installation, so readers on a stock
  python3.13 don't follow the note and get nothing.
- Drop "allowing for true multi-threading parallelism". RxPY is not
  tested under free threading (no 3.13t/3.14t in the CI matrix), so the
  docs should describe CPython's capability, not imply RxPY exploits it.
- The GIL prevents concurrent bytecode execution, not "accessing the
  same line of code simultaneously".
- Link the official free-threading howto, and note in the parallelism
  section that pure-Python work can scale on a free-threaded build.

Formatting:
- Remove five lines of trailing whitespace and a double space.
- Re-wrap to the file's ~80 column convention (seven lines were 89-107
  characters, against three over 88 in the rest of the file).
- RxPy -> RxPY.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants