Loosen numpy constraint from ==2.2.0.* to ==2.2.*#162
Merged
Conversation
The inline comment already documents the intent as "NumPy 2.2.x supports Python 3.10-3.13", but ==2.2.0.* pins to exactly 2.2.0 and excludes the 2.2.1-2.2.6 patch releases (bug/security fixes). The dependency used a minor-level pin (numpy==1.24.*) before PR apache#108 bumped it to 2.2.0.*, so the patch-level pin appears unintentional. Loosen to ==2.2.* to match the documented intent and allow 2.2.x patch updates. Regenerate uv.lock (numpy 2.2.0 -> 2.2.6). Full test suite (112 tests) and tox lint pass against numpy 2.2.6.
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
2 participants
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.
What
Loosen the numpy version constraint for Python < 3.14 from
==2.2.0.*to==2.2.*.Why
The inline comment in
pyproject.tomlalready documents the intent as:However,
==2.2.0.*is a prefix match that pins to exactly2.2.0(numpy publishes no 4-segment versions), so it excludes the2.2.1–2.2.6patch releases along with their bug/security fixes. This looks unintentional: the dependency was a minor-level pin (numpy==1.24.*) until #108 bumped it to2.2.0.*, where the natural equivalent would have been2.2.*.Loosening to
==2.2.*makes the constraint match the documented intent and lets users pick up 2.2.x patch releases, while still excluding 2.3 (which is handled separately for Python ≥ 3.14).Changes
pyproject.toml:numpy==2.2.0.*→numpy==2.2.*(Python < 3.14)uv.lock: regenerated viauv lock(numpy2.2.0→2.2.6)Testing
uv run pytest(tests + perf): 112 passed against numpy 2.2.6uv run tox -e lint: passed (ruff, autoflake, isort, flake8, license headers)