Uh oh!
There was an error while loading. Please reload this page.
chore(deps): drop unused numpy and pandas dependencies - #125
Merged
Conversation
Neither package is imported anywhere in the analyzer -- `git grep` finds first-party hits only in the vendored xarray test fixture and in a comment in the Homebrew formula generator. Both were nonetheless declared in `[project].dependencies` with tight upper caps (`numpy<1.24` below Python 3.11, `numpy<2.0` above it). Those caps forced resolution onto numpy releases with no prebuilt wheel for some targets -- Red Hat UBI images in particular -- so `pip install codeanalyzer-python` fell back to building numpy from source and failed. On Python 3.11+ numpy now disappears from the resolved tree entirely, since ray 2.55 declares no numpy dependency and pandas was its only other route. On Python 3.9/3.10 `ray==2.0.0` still pulls numpy in transitively; raising that pin carries real compatibility risk and is left for a separate change.
rahlkforce-pushed
the
chore/issue-124-drop-numpy-and-pandas
branch
from
August 18, 2026 14:37
ebc6adf to
fec0f14Compare
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 freeto 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.
Closes#124.
What
Removes the
numpyandpandasentries from[project].dependencies. Neitheris imported anywhere in the analyzer —
git grep -I "numpy\|pandas"findsfirst-party hits only in the vendored
xarraytest fixture and in comments inpackaging/homebrew/generate_formula.sh(also updated here).Why
The declarations carried tight upper caps (
numpy>=1.21.0,<1.24.0below Python3.11,
<2.0.0above it). Those caps pinned installs to numpy releases with noprebuilt wheel for some targets — Red Hat UBI images in particular — so
pip install codeanalyzer-pythonfell back to building numpy from source andfailed. Same failure class as #19, except this dependency buys nothing.
pandaswas the only remaining route to numpy on modern interpreters:ray2.55 declares no numpy dependency, so removing both drops numpy from the
resolved tree entirely on Python 3.11+.
Verification
Full test suite run with numpy absent from the environment.
Not in scope
On Python 3.9/3.10 the
ray==2.0.0pin still pulls numpy in transitively, souv tree --python-version 3.9still reportsnumpy v1.23.5. Raising that rayfloor carries real compatibility risk and is deliberately left out.
The same change is backported to
release/0.3.xand released as0.3.2forconsumers pinned to the 0.3 line.