Build wheels for Python 3.15 - #346
Closed
p-r-a-v-i-n wants to merge 1 commit into
Closed
p-r-a-v-i-n wants to merge 1 commit into
p-r-a-v-i-n wants to merge 1 commit into
Conversation
Owner
|
I will publish new wheels with the new release. Don't rush me. |
1 of 3 tasks
Owner
|
FYI, wheels for 3.15 and 3.15t are on PyPI now. |
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.
Changes
Fixes #344
cbor2 already declares and tests support for Python 3.15, but release 6.1.4 does not contain CPython 3.15 wheels because the publishing workflow uses cibuildwheel 4.1.
cibuildwheel 4.2 enables CPython 3.15 builds by default using the ABI-stable Python 3.15 RC. This update will make the next cbor2 release publish cp315 wheels
Refs docs:
Checklist
If this is a user-facing code change, like a bugfix or a new feature, please ensure that
you've fulfilled the following conditions (where applicable):
tests/) which would fail without your patchdocs/), in case of behavior changes or newfeatures
docs/versionhistory.rst).