Repository navigation
chore/Python-version-pin · L-261023-028959 - #96
Merged
Merged
Conversation
…ell's version .python-version names 3.13, the version the Makefile defaulted to. The Makefile reads it and exports the chosen version as UV_PYTHON, so PYTHON_VERSION or UV_PYTHON still select another one and every uv command, uv sync included, keeps .venv on it; before, PYTHON_VERSION=3.11 make install left an existing .venv on its old Python. The lint and test matrices set UV_PYTHON for the whole job instead of prefixing one command, and end by asserting that .venv ran the version the job names. The docs check keeps 3.11 through a job-level UV_PYTHON, and the docs deploy installs the pinned Python instead of the newest 3.x. CONTRIBUTING.md, which the docs site includes, says where the interpreter is pinned and how to try another. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01TuqArJByf4EdN7khSDRiPe
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
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.
cocode now pins its development interpreter to 3.13 in
.python-version, and the Makefile exports it asUV_PYTHON, somake installbuilds on the pin andPYTHON_VERSION=3.11 make installreally rebuilds on 3.11, which it silently did not before. The lint and test matrices setUV_PYTHONper cell and end by asserting the interpreter they ran, the docs check keeps 3.11 at job level, and the docs deploy reads the version from the file.Closes L-261023-028959
🤖 Generated with Claude Code
https://claude.ai/code/session_01TuqArJByf4EdN7khSDRiPe
Summary by cubic
Pins the development interpreter to 3.13 in
.python-versionand has the Makefile and CI read it, so the terminal, editor, and CI all agree on one Python version.Before,
PYTHON_VERSION=3.11 make installsilently left an existing.venvon its old Python; now it rebuilds on the version named, and a plainmake installreturns the environment to the pin. The lint and test matrix jobs setUV_PYTHONper version and fail unless.venvran the version the job names. The docs check keeps 3.11 at job level, and the docs deploy installs the pinned version from the file.Closes L-261023-028959
Written for commit f5b9fa6. Summary will update on new commits.