Numpy2 adaptation - #1231
Merged
Merged
Conversation
Open
sergey-yaroslavtsev
force-pushed
the
numpy
branch
from
July 10, 2026 12:25
d2bbfb6 to
31f377b
Compare
Collaborator
Author
|
same confusion as in #1230. |
woutdenolf
approved these changes
Jul 10, 2026
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.
Bug detected on ID26.
Some numpy methods, type, ... were changed in version 2+.
this PR switch
numpy.float int complextonumpy.float64 int64 complex128+infinitytoinfalso conditionally
trapztotrapezoid(to keep compatibility with old version of numpy)finally
numpy.core.records.recarraytonumpy.recarray(numpy2 make do not likecore) - I could not find any reason to use it fromcore- let me know if i am wrong about itbased on #1222