Fix NumPy 2.0 compatibility by replacing removed np.alltrue with np.all - #42
Merged
Conversation
added 2 commits
July 1, 2026 20:19
np.alltrue was removed in NumPy 2.0; it was a plain alias for np.all with no behavior difference. This was breaking Image.__eq__ and test assertions on modern NumPy, causing 32/39 tests to fail.
…ss-validation details Document mpstool.variogram and mpstool.cv_metrics, which were previously unmentioned, plus the tools/ CLI scripts and the note that these two modules require an explicit import.
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.
np.alltrue was removed in NumPy 2.0; it was a plain alias for np.all with no behavior difference. This was breaking Image.eq and test assertions on modern NumPy, causing 32/39 tests to fail.