fix: raise the Python floor to 3.14 - #9
Merged
Merged
Conversation
3.14 is the current stable line and the suite moves off 3.12 together. - requires-python is now >=3.14 - .python-version follows it to 3.14; left at 3.12 it contradicts the floor and uv refuses the environment - uv.lock re-resolved under CPython 3.14.4: 86 packages, and NO package dropped. The 517 removed lines are all cp311/cp312/cp313 wheel rows, including the compiled numpy and scikit-learn sets - the mypy python_version comment claimed it matched the minimum supported version, which the floor bump made false ruff target-version, mypy python_version, ty python-version and vermin targets all stay on 3.12 deliberately, matching scalo-py and hyperi-ci. At py314 the ruff formatter strips the parentheses from multi-exception except clauses (PEP 758), so the suite holds one static-analysis level rather than splitting it per repo.
|
Released in v3.5.1 — https://github.com/hyperi-io/logreducer/releases/tag/v3.5.1 |
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
1 participant
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.
Part of moving the whole suite to 3.14. The owner's rule: any part of the suite still on 3.12 moves.
requires-pythongoes>=3.12->>=3.14.python-versionfollows to3.14. Left at 3.12 it contradicts the floor and uv refuses the environment -- this repo is the only one of the three with that fileuv.lockre-resolved under CPython 3.14.4. 86 packages, and no package dropped -- the 517 removed lines are all cp311/cp312/cp313 wheel rows, confirmed bygit diff uv.lock | rg "^-name = "returning nothing. That includes the compiled sets, numpy and scikit-learnpython_versioncomment said "Matches minimum supported version", which the floor bump made false. Reworded rather than left wrongFour analysis pins deliberately stay on 3.12: ruff
target-version, mypypython_version, typython-versionand vermintargets. That matches scalo-py and hyperi-ci. At py314 the ruff formatter strips the parentheses from multi-exceptionexceptclauses (PEP 758). hyperi-ci has a sharper reason than we do -- it loadsversion_source.pyby path with an older interpreter before any install -- but holding the whole suite at one static-analysis level beats splitting it per repo..hyperi-ci.yamlcarries no Python version and there is no Dockerfile, so nothing else in this repo pins one.NOT verified: nothing was installed or imported under 3.14. The lock resolving cleanly with every compiled dependency is the evidence here; CI is what proves it runs.
Note scalo-py #28 is still open -- the suite is not actually on 3.14 until that lands.
Done when CI is green.