Update code to support newest NumPy versions (2.x) #345
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.
This PR removes the artificial constraints blocking OpenPIV from using the newest NumPy versions, including NumPy 2.3.2.
Problem
The current version constraints in
pyproject.tomlusednumpy = "^1.21.6"which translates to>=1.21.6,<2.0.0, artificially blocking users from installing NumPy 2.x. Additionally, the code contained deprecatednp.floatusage that would cause errors in NumPy 2.x.Changes
Fixed deprecated NumPy usage:
openpiv/pyprocess.pyline 876:np.float→np.float64(in docstring example)Updated version constraints:
pyproject.toml: Changednumpy = "^1.21.6"tonumpy = ">=1.21.6"setup.py: Changed'numpy'to'numpy>=1.21.6'Testing
Impact
Before:
pip install openpivwould install NumPy 1.26.4 (latest allowed by constraints)After:
pip install openpivcan install the latest NumPy 2.3.2This change is fully backwards compatible - existing installations continue to work unchanged, but new installations can benefit from the latest NumPy improvements and bug fixes.
Fixes #344.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.