docs(agents): the declared Python floor is type-checked, never run #7

Merged
jlxq0 merged 1 commit from docs/python-floor into master 2026-08-26 06:30:21 +00:00
Owner

Fork patch. A note about what this repo's CI does and does not exercise.

requires-python = ">=3.11", .python-version pinning 3.13, uv honouring it, and the Dockerfile pinning python:3.13-slim-bookworm by digest. CI and the image agree with each other, and neither runs the floor. mypy is configured at python_version = "3.11", which type-checks it and executes nothing.

Checked rather than recorded as an open gap: the suite passes on 3.11.15, all 66 tests, in a throwaway venv. So the declaration is true today. It is simply not something CI can keep true, and a change needing 3.12+ would land green.

No 3.11 job. Exercising a version nobody in this fleet runs buys less than the noise costs.

The floor is not raised to 3.13 either, which is the other way to make the declaration honest. Upstream publishes this package to PyPI at >=3.11, so narrowing it is divergence to carry or send upstream rather than a local tidy. Both options are written down so the next reader does not re-derive them.

**Fork patch.** A note about what this repo's CI does and does not exercise. `requires-python = ">=3.11"`, `.python-version` pinning 3.13, uv honouring it, and the Dockerfile pinning `python:3.13-slim-bookworm` by digest. CI and the image agree with each other, and neither runs the floor. mypy is configured at `python_version = "3.11"`, which type-checks it and executes nothing. Checked rather than recorded as an open gap: **the suite passes on 3.11.15, all 66 tests**, in a throwaway venv. So the declaration is true today. It is simply not something CI can keep true, and a change needing 3.12+ would land green. **No 3.11 job.** Exercising a version nobody in this fleet runs buys less than the noise costs. **The floor is not raised to 3.13 either**, which is the other way to make the declaration honest. Upstream publishes this package to PyPI at `>=3.11`, so narrowing it is divergence to carry or send upstream rather than a local tidy. Both options are written down so the next reader does not re-derive them.
docs(agents): the declared Python floor is type-checked, never run
All checks were successful
CI / python (pull_request) Successful in 26s
CI / docker (pull_request) Successful in 11s
13ed48086a
`requires-python = ">=3.11"` with `.python-version` at 3.13, uv honouring it
and the Dockerfile pinning 3.13 by digest: CI and the image agree with each
other and neither runs the floor. mypy is configured at 3.11, which
type-checks it and executes nothing.

Checked rather than left as a gap: the suite passes on 3.11.15, all 66 tests,
in a throwaway venv. The declaration is true today; it is just not a thing CI
can keep true, and a change needing 3.12+ would land green.

No 3.11 job — exercising a version nobody in this fleet runs buys less than the
noise costs. Raising the floor to 3.13 is the other way to make the declaration
honest, and is not taken: upstream publishes this package to PyPI at `>=3.11`,
so narrowing it is divergence to carry or send up rather than a local tidy.
Written down so the next reader does not re-derive both options.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EfH9dv5Ub8c9PRxipsBXBe
jlxq0 merged commit 04d9e1cb60 into master 2026-08-26 06:30:21 +00:00
jlxq0 deleted branch docs/python-floor 2026-08-26 06:30:21 +00:00
Sign in to join this conversation.
No description provided.