MAINT: should not be using np.float64() on arrays #19076
Merged
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 is related to #18781.
When performing
integrate.simpson(np.array([1,2,3.]), x=np.array([1, 2, 3.]))
in a script I was experiencingDeprecationWarning
s of the form reported #18781. The warning is also emitted with length 4 arrays.These were not visible in the scipy test suite, probably because this line meant that all
DeprecationWarning
s, including the numpy warnings, weren't visible.The numpy warnings were caused by the lines:
If
h[sl0])
has length 1, then thenp.float64
call raises the warning (similar argument forh1
). The warning doesn't occur if the length is greater than 1. The solution is to usenp.ndarray.astype
.h[sl0]
will always be an array, so casting to float should always work. The test suite already examines a case where the integrate set has length 4.