Added ruff rule to check for numpy2.0 compatibility #227
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.
Description
What is this PR
Why is this PR needed?
Numpy 2.0 was released yesterday, containing some breaking API changes (syntax deprecations).
The Numpy devs have written a migration guide, and have even provided a ruff linting rule - NPY201 - that "Checks for uses of NumPy functions and constants that were removed from the main namespace in NumPy 2.0".
What does this PR do?
It add NPY201 to the ruff lint config.
I also run
pre-commit run -a
and thankfully nothing came up. Nevertheless I'll leave this rule in, so that no deprecated syntax creeps in.References
n/a
How has this PR been tested?
Existing tests pass locally and in CI.
Is this a breaking change?
No.
Does this PR require an update to the documentation?
No.
Checklist: