-
Notifications
You must be signed in to change notification settings - Fork 300
SPEC0 - support Python 3.12 to 3.14 #6816
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.
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please see: SciTools/.github#234
|
The failures appear to come from Python 3.14 incompatibilities in dependencies:
These prevent all of Iris' CI running correctly. However the vast majority of tests have run, and have passed, including many tests which exercise I believe we are therefore able to provide Python 3.14 compatibility, although we're not yet able to provide support due to these CI problems preventing full coverage. |
|
|
With what we know about VTK+PyVista and new versions of Python: we should be considering separating the |
* pytest skips added to geovista experimental tests if import missing.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6816 +/- ##
==========================================
- Coverage 90.43% 90.18% -0.26%
==========================================
Files 91 91
Lines 24839 24822 -17
Branches 4656 4656
==========================================
- Hits 22463 22385 -78
- Misses 1608 1669 +61
Partials 768 768 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
⏱️ Performance Benchmark Report: 242ca87Performance shiftsFull benchmark resultsGenerated by GHA run |
🚀 Pull Request
Description
Scientific Python - SPEC 0 — Minimum Supported Dependencies
Closes #6775
Slight hiccup:
3.14.1patch release. See 🦌 Iris 3.14.x #6626 (comment)So here are my proposed steps:
v3.14.xrelease branch, which will give the3.14.1release compatibility with Python 3.14.v3.14.xtomain; this needn't wait for the release itself.main.The above pattern will avoid Git conflicts and maintain maximum integrity in our Git history, avoiding situations where a change has two different SHAs depending on which branch it is on.
Terminology
Consult Iris pull request check list
Add any of the below labels to trigger actions on this PR: