Fix CI errors in NumPy 2.3.1 #1163
Merged
Conversation
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
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.
This PR fixes a couple of CI errors that arose in NumPy 2.3.1 and that hadn't shown up prior to this:
optimal.py, there was a bug in saving old values of an array, wherecopy()should have been used.lti.py, there seems to be a difference in the waynumpy.multiplyreturns values (perhaps due to rounding?) that was causing transfer functions with complex coefficients when usingc2d.Fixes for both are very small and I'll merge this quickly so that I can release 0.10.2 this weekend.