fix: Make type hints compatible with numpy >= 2.4.x#260
Merged
Conversation
1 task
Contributor
csjall
approved these changes
Feb 4, 2026
bkeryan
changed the title
bkeryan
changed the title
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this Pull Request accomplish?
Update to NumPy 2.4.2. Release notes: https://numpy.org/doc/stable/release/2.4.0-notes.html
Make necessary retrofits:
npt.DTypeLikeno longer includes None, so we must usenpt.DTypeLike | Nonewhen we want to accept None.np.unpackbits()andndarray.reshape()now have shape typing, so we should not reuse variable names when reshaping arrays.Why should this Pull Request be merged?
NumPy 2.4 includes several type hint changes which affect our code.
What testing has been done?
Ran mypy, pyright, pytest