Skip to content

Update "One-time ABI Breakage" #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hugovk merged 1 commit into from
Oct 1, 2026
+2 −2
Merged

Update "One-time ABI Breakage" #152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/posts/language-summit-2026-lightning-talks/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,8 @@ Free-threaded Python has not promised Stable ABI compatibility
for its object layout, unlike non-free-threaded Python, which exposed
details about `ob_refcnt` in the Stable ABI.

It was at this point that it began slowly dawning on Mark, to his horror, that free-threaded
Python may be solving his problem. After free-threading becomes the new Python default,
There didn't appear to be much appetite for breaking the existing Stable ABI.
After free-threading becomes the new Python default,
the Stable ABI that exposes the object header internals will be no more, and Mark
and team can make changes to the object header more freely. We’ll just have to be patient!

Expand Down
Loading