SPEC0 - support Python 3.12 to 3.14 #6816
Open
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
github-actions
bot
added
the
benchmark_this
2 tasks
![scitools-ci[bot]](https://avatars.githubusercontent.com/in/212324?s=60&v=4){kind=small}
Contributor
Author
|
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. |
This was referenced Nov 25, 2025
Contributor
Author
|
Contributor
Author
|
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:
|
Contributor
⏱️ Performance Benchmark Report: 242ca87Performance shiftsFull benchmark resultsGenerated by GHA run |
Contributor
⏱️ Performance Benchmark Report: 48ea84dPerformance shiftsFull benchmark resultsGenerated by GHA run |
Contributor
|
@pp-mo - the following changes were made to get the CI working without
Possible alternative to the above (w.r.t. doctests):Bill and I have been chatting about the possibility of dynamically updating the docstring ( I've run out of time to explore this further now, but if you think it sounds doable, then I'll have a play next week. |
Contributor
|
Also, something else to consider is that we only run doctest for the newest python version, so the doctests for geovista are not being run at all at the momnet. Should we consider adding in a |
Contributor
Author
A temporary switch to only Python 3.13 for doctests would be my favoured approach, so long as we've captured it in an issue for future. |
Contributor
⏱️ Performance Benchmark Report: 0937e7dPerformance shiftsFull benchmark resultsGenerated by GHA run |
Contributor
⏱️ Performance Benchmark Report: cf25ec3Performance shiftsFull benchmark resultsGenerated by GHA run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
🚀 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: