Skip to content

CI: New NumPy release breaking Numba in our CI #61616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
datapythonista opened this issue Jun 9, 2025 · 2 comments
Open

CI: New NumPy release breaking Numba in our CI #61616

datapythonista opened this issue Jun 9, 2025 · 2 comments
Labels
CI Continuous Integration Dependencies Required and optional dependencies

Comments

@datapythonista
Copy link
Member

pandas/tests/groupby/aggregate/test_numba.py:19: in 
    numba = pytest.importorskip("numba")
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E   pytest.PytestDeprecationWarning: 
E   Module 'numba' was found, but when imported by pytest it raised:
E       ImportError('Numba needs NumPy 2.2 or less. Got NumPy 2.3.')
E   In pytest 9.1 this warning will become an error by default.
E   You can fix the underlying problem, or alternatively overwrite this behavior and silence this warning by passing exc_type=ImportError explicitly.
E   See https://docs.pytest.org/en/stable/deprecations.html#pytest-importorskip-default-behavior-regarding-importerror

Source: https://github.com/pandas-dev/pandas/actions/runs/15541539524/job/43753280349#step:9:76

Somehow related: numba/numba#10105

@pandas-dev/pandas-core I guess it's not the first time this happens, since seems that Numba has been raising ImportError instead of pining the dependencies for at least one more version. Doesn't seem like we should be pinning NumPy ourselves. Any idea how this was fixed before if it already happened, or what should we do to fix the CI?

@datapythonista datapythonista added CI Continuous Integration Dependencies Required and optional dependencies labels Jun 9, 2025
@TomAugspurger
Copy link
Contributor

This was probably fixed by conda-forge/numba-feedstock#157.

I think conda-forge/conda-forge-repodata-patches-feedstock#1039 will fix this with no change needed on our part, or you could temporarily add that pin until that repo data fix is in.

@datapythonista
Copy link
Member Author

Ah, amazing, thanks a lot for the info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Dependencies Required and optional dependencies
Projects
None yet
Development

No branches or pull requests

2 participants