Build abi3.abi3t wheels for CPython 3.15+ - #15496
Conversation
alex
left a comment
There was a problem hiding this comment.
@reaperhulk do we want to drop 3.14t wheels as soon as we're doing abi3t wheels? I strongly prefer that, but curious for your views.
| with: | ||
| python-version: ${{ inputs.python-version }} | ||
| architecture: ${{ inputs.arch }} | ||
| allow-prereleases: ${{ inputs.python-version == '3.15t' }} |
There was a problem hiding this comment.
We do not want to ever use allow-prereleases. If you want to use a pre-release, you should specify the version.
There was a problem hiding this comment.
I removed the usage of allow-prereleases.
Depending on the decision by maintainers regarding when this should be available, the modifications could be reduced for Windows if after 3.15.0.final (they can always be reverted after 3.15.0.final if this goes in before that)
Normally I’d be strongly against that, but I think free-threaded consumers are pretty aggressive in their upgrades right now. However, if we’re shipping abi3t day 1 of 3.15 we’re cutting off wheels for every existing free-threaded consumer so I think we need one release with both? |
|
Well, we'd need to choose when we want to do a release with this. Are we gonig to try to have it for 3.15 release day? |
This is a follow-up on #15063 which updates the wheel-builder workflow to build abi3.abi3t wheels for CPython 3.15+ now that CPython 3.15.0rc1 is available.
From #15063:
Release automation uses the wheel-builder workflow updated here.
Python 3.15 has been added in project classifiers.