rm numarray, NumPy 2.0 compatibility #408
Merged
Conversation
This file contains 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
For NumPy 2.0 compatibility.
eoyilmaz
approved these changes
Oct 14, 2024
|
Thank you @nschloe 👍 |
Wedge009
added a commit
to Wedge009/displaycal-py3
that referenced
this pull request
Oct 16, 2024
eoyilmaz#408 removed the choice between numpy and numarray and thus removed the _Numeric attribute. May as well us numpy directly now.
This was referenced Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I replaced
np.sometruebynp.anyfor NumPy 2.0 compatibility. While at it, I also removed traces of numarray, an early Python array package which had its last release in 2006.