Repository navigation
chore(deps): raise dependency floors to 3.10 minimums and drop pytest cap - #1107
Conversation
… cap Several dependency-group minimums predated the project's Python 3.10 floor (no cp310 support in those releases). Raise each to its first 3.10-supporting release and sync tests/constraints.txt. Also drop the `pytest < 7.5` cap from the typing group: it pinned pytest across the whole universal lockfile even though the test group wants the latest. The mypy ~= pin is intentionally kept (it only pins the type-checker, not shared deps). Assisted-by: ClaudeCode:claude-opus-4.8
Assisted-by: ClaudeCode:claude-opus-4.8
🤖 Reasons 🤖
Yes. Two categories: strict "first release that declared/shipped 3.10 support," and a few where I rounded up past that to avoid a known-bad early release — I'll flag those explicitly so you can decide. Strict first-3.10 release (current floor predated it; bumped to exactly the first supporting version):
Rounded up past the strict minimum (judgment calls — tell me if you'd rather use the strict value):
Kept (not bumped), with reasons:
The strict-first-3.10 values came from PyPI classifier/upload-date metadata; the verification ( |
| "pytest >= 6.2.5", | ||
| "pytest-mock >= 3.7.0", |
There was a problem hiding this comment.
We can delete these two lines, I think? We need to install the test group to type check the test folder anyway.
There was a problem hiding this comment.
Reworked to use a shared group. (also pulled a change from #1106 and rewrote the changelog entry).
Signed-off-by: Henry Schreiner <henryfs@princeton.edu>
Some of these are more technically correct, but the old version worked. Minor bumps to lower floors seem fine, though? Happy to revert some if someone prefers. I'll bump mypy in a followup.
🤖 AI text below 🤖
What
The dependency-group minimums were not revisited after the project moved to
requires-python >= 3.10, so several floors point at releases that predate genuine 3.10 support (no cp310 wheels / never declared the classifier). This raises each to its first 3.10-supporting release and removes a cap that constrained the shared lockfile.Floor bumps
Verified against PyPI metadata and a real Python 3.10 interpreter:
pytestpytest-covpytest-mockpytest-rerunfailurespytest-xdistwheelsetuptools_scmfilelockcoverage[toml]diff_covertyping-extensionsvirtualenv(extra)tests/constraints.txtsynced to match:setuptools_scm6.3.1→6.4.2 (6.3.1 itself predates 3.10),wheel0.36.0→0.37.0.Cap removed
pytest < 7.5in thetypinggroup pinned pytest across the entire universal lockfile even though thetestgroup wants the latest. Replaced withpytest >= 6.2.5.Kept deliberately
setuptools >= 56.0.0— confirmed it builds a wheel on real Python 3.10, so the floor is valid.mypy ~= 1.18.2— only pins the type-checker itself, not shared deps, so it does not constrain the lockfile. Intentional tool pin.Verification
uv lock --dry-runresolves cleanly (pytest now floats to latest)uv run --group mypy mypypasses against the uncapped pytestprek -apasses