Skip to content

Conversation

@dstansby
Copy link
Contributor

@dstansby dstansby commented Jan 2, 2026

Since it's been about six months since SPEC recommended removing support for NumPy 1.26, this bumps the minimum version to 2.0. This duplicates work in #3564, but I figured that it might be easier to do the version bumps (numpy and Python) independently since #3564 appears to have grown in scope quite a bit. ping @ilan-gold - I hope that's okay?

My motivation for doing this is the slowest test in the matrix seems to be the one with NumPy 1.26, so I'm hoping this improves the total time GH actions takes to run all the tests to completion.

@codecov
Copy link

codecov bot commented Jan 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.89%. Comparing base (8207dd3) to head (62e1de5).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3636      +/-   ##
==========================================
- Coverage   60.90%   60.89%   -0.01%     
==========================================
  Files          86       86              
  Lines       10174    10174              
==========================================
- Hits         6196     6195       -1     
- Misses       3978     3979       +1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ilan-gold
Copy link
Contributor

No worries! As you can see that PR is mostly other things anyway

matrix:
python-version: ['3.11', '3.12', '3.13']
numpy-version: ['1.26', '2.2']
numpy-version: ['2.0', '2.2']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After setting the minimum version to 2.0, do we still need different numpy versions in the test matrix?

Copy link
Contributor

@d-v-b d-v-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dstansby! We should decide on a testing strategy for different numpy versions, but that shouldn't stop this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants