Add initial support for abi3.abi3t tag from PEP 803#5193
Draft
Add initial support for abi3.abi3t tag from PEP 803#5193
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of changes
PEP 803 proposes a free-threaded stable ABI. I'm working on ecosystem support for a free-threaded stable ABI and end-to-end tests for PEP 803. There is experimental support for an opaque PyObject ABI in currently CPython 3.15 alphas.
This PR isn't mergeable until PEP 803 is accepted and pypa/packaging#1099 is available in a released version of
packaging.It possible that in the future setuptools might want to add a new config knob to go along with
py-limited-api(py-target-abi3tmaybe?), but that will require PEP 803 to be accepted in its current form. IMO for now requring a free-threaded interpreter to build an abi3t wheel is fine.Pull Request Checklist
newsfragments/.(See documentation for details)