Skip to content

PEP 803: Add new Discussions-To link #4818

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
Feb 16, 2026
Merged

PEP 803: Add new Discussions-To link #4818

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
5 changes: 3 additions & 2 deletions peps/pep-0803.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,15 @@
PEP: 803
Title: "abi3t": Stable ABI for Free-Threaded Builds
Author: Petr Viktorin <encukou@gmail.com>
Discussions-To: https://discuss.python.org/t/103628
Discussions-To: https://discuss.python.org/t/106181
Status: Draft
Type: Standards Track
Requires: 703, 793, 697
Created: 19-Aug-2025
Python-Version: 3.15
Post-History: `08-Sep-2025 <https://discuss.python.org/t/103628>`__,
`20-Nov-2025 <https://discuss.python.org/t/104976>`__,
`16-Feb-2026 <https://discuss.python.org/t/106181>`__,


Abstract
Expand Down Expand Up @@ -641,7 +642,7 @@ Reusing ``Py_GIL_DISABLED`` to enable the new ABI
It would be possible to select ``abi3t`` (rather than ``abi3``) when the
``Py_GIL_DISABLED`` macro is defined together with ``Py_LIMITED_API``.

This would require annoying fiddling with buil flags, and make it
This would require annoying fiddling with build flags, and make it
especially cumbersome to target *both* ``abi3`` and ``abi3t`` at the same time.


Expand Down
Loading