Repository navigation
WHL: add wheels for CPython 3.15 - #1902
Merged
Merged
Conversation
zssherman
approved these changes
Oct 17, 2026
Collaborator
|
Thanks as always for the PR @neutrinoceros ! Everything looks good, I'm just waiting on the final test to pass |
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.
PR tags (required)
Select all that apply.
What changed
cftime now has cp311-abi3 wheels up on PyPI, so it won't be blocking anytime soon (at least for GIL-enabled builds)
Why
unblocks dependees that want to try out the newest and greatest Python.
Issues closed
None
Target version
Select one.
Validation
Mark each item as done or N/A. Add one short evidence line for each item.
I ran pre-commit or ruff
I ran tests
AI usage & manual verification
If AI tools were used, complete this section.
Manual verification
Mark each item as done or N/A. Add one short evidence line or N/A reason for each item.
[n/a] For scientific/algorithmic or result-changing PRs, I provided an example notebook.
[n/a] I compared before-and-after outputs and stated whether results changed.
[n/a] I checked results against a known baseline or expected values.
[n/a] I manually exercised relevant edge cases.
[n/a] I checked backward compatibility or API behavior.
Impact note (optional): breaking behavior, scientific output shift, or user-visible behavior.