migrate the other CI to python 3.11 #8416
Merged
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.
(namely, additional CI and upstream-dev CI)
python=3.11
has been released more than a year ago andpython=3.12
is out as well, which means that it is a good idea to migrate sooner than later.Regarding
python=3.12
, usually it isnumba
that keeps us from testing on a newpython
version for some time, wherenumbagg
andsparse
are the only dependencies that would use it. Should we create a environment without those two dependencies and switch back to the normal one oncenumba
supports the new python version?We still have the special environment files for
python>=3.11
because the normal ones still includecdms2
. We deprecated that back in May – not sure which release that ended up in – but sincecdms2
will be abandoned end of this year, that's when we're free to drop support and merge both environments (though maybe we can justify dropping support earlier?)