fix: raise the Python floor to 3.14 - #26
Merged
Merged
Conversation
3.14 is the current stable line and the suite moves off 3.12 together. Both projects in this repo carry a floor, so both move. - build/pyproject.toml and vector-vrl/pyproject.toml are now >=3.14 - the three per-minor classifiers go, replaced by "Python :: 3 :: Only". With a 3.14 floor the 3.12 and 3.13 entries claimed support the package refuses, and the policy is that requires-python carries the version and classifiers never repeat it - both locks re-resolved under CPython 3.14.4. vector-vrl drops typing-extensions, which pytest-asyncio pulled behind a python_full_version < '3.13' marker that can no longer be true. build drops nothing vector-bindings keeps abi3-py312. The stable ABI is forward compatible, so a py312 abi3 wheel already runs on 3.14, and narrowing it to abi3-py314 would cut wheel reach for no gain.
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. This repo carries two Python projects and both had a floor.
build/pyproject.tomlandvector-vrl/pyproject.tomlboth go>=3.12->>=3.14The three per-minor classifiers are removed, replaced by
"Programming Language :: Python :: 3 :: Only". This is the one repo in the sweep that had them, and with a 3.14 floor the3.12and3.13entries were claiming support the package now refuses. The policy is thatrequires-pythoncarries the version and classifiers never repeat it -- otherwise they need updating every release and can drift, which is exactly what happened here.What moved in the locks:
vector-vrldropstyping-extensions, and only that. It was never a direct dependency --pytest-asynciopulled it behindmarker = "python_full_version < 3.13", which a 3.14 floor can never satisfy.builddrops nothing. Verified withgit diff -- */uv.lock | rg "^-name = ", which returns that one line.vector-bindingsdeliberately keepsabi3-py312. PyO3's stable ABI is forward compatible, so a py312 abi3 wheel already runs on 3.14 -- that is the point of building against it. Narrowing toabi3-py314would cut wheel reach and buy nothing. The comment atvector-bindings/Cargo.toml:14already says one wheel per platform serves 3.12+, and that stays true.NOT changed:
build/wheel_smoke_check.py:23mentions "3.12" inside a docstring explaining what a wheel filename tag looks like. It is an illustration, not a pin.NOT verified: nothing was built or installed under 3.14, and no wheel was produced. Lock resolution is the evidence here; CI is what proves the bindings still build.
Done when CI is green per job.