Change supported Python versions to 3.10-3.14#108
Merged
Conversation
Gerrrr
force-pushed
the
upgrade-python
branch
from
81cd45c to
77296c3
Compare
henrikingo
approved these changes
Dec 7, 2025
| [project] | ||
| name = "apache-otava" | ||
| version = "0.7.0" | ||
| version = "1.0.0" |
Contributor
There was a problem hiding this comment.
Yeah, probably about time.
| "expandvars>=0.12.0", | ||
|
|
||
| # For Python 3.10: last series that supports it | ||
| "scipy>=1.15,<1.16; python_version < '3.11'", |
Contributor
There was a problem hiding this comment.
Do we need to support all of these python versions? I would be more aggressive in jumping to the newest and dropping older versions.
Contributor
Author
There was a problem hiding this comment.
I think it is a solid default to support all officially supported Python versions.
Reasons:
- It seems reasonable to me for an infrastructure library to be biased towards being conservative. Stability or lack of maintenance may be as important of a feature as new shiny features for this kind of software. For example, all Otava installations I care about at the moment have been running with 0 maintenance for years, which I am proud of.
- It does not cost us that much extra effort - Scipy has been the only library that caused an issue and we only use 1 simple method out of it - . I would not even mind extracting that method and dropping that dependency.
Lines 123 to 126 in 3154520
WDYT?
Contributor
There was a problem hiding this comment.
Ok lets try it
As for multithreading and such, we could implement it in a way so that the default is 1 thread and it can only have some other value if python version is 3.14.
Gerrrr
pushed a commit
that referenced
this pull request
Jun 2, 2026
The inline comment already documents the intent as "NumPy 2.2.x supports Python 3.10-3.13", but ==2.2.0.* pins to exactly 2.2.0 and excludes the 2.2.1-2.2.6 patch releases (bug/security fixes). The dependency used a minor-level pin (numpy==1.24.*) before PR #108 bumped it to 2.2.0.*, so the patch-level pin appears unintentional. Loosen to ==2.2.* to match the documented intent and allow 2.2.x patch updates. Regenerate uv.lock (numpy 2.2.0 -> 2.2.6). Full test suite (112 tests) and tox lint pass against numpy 2.2.6.
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
2 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.
This PR drops support for Python 3.8, 3.9 and adds support for 3.11, 3.12, 3.13, 3.14. It also updates all dependencies to latest versions supporting all officially supported Python versions.