BUG: Respect dtype of all-zero argument to poly1d#17577
Merged
Conversation
Fixes numpygh-16354. Previously np.poly1d(z).coeffs.dtype would always be np.float64 for zero array z, regardless of z's dtype.
eric-wieser
reviewed
Oct 18, 2020
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Member
|
Doctests are failing. Since this appears to change behavior it needs a release note. The release notes snippets are in |
Member
|
Thanks @cjblocker |
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
4 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.
Fixes gh-16354.
Previously,
np.poly1d(z).coeffs.dtypewould always benp.float64for zero arrayz, regardless ofz's dtype.This led to unexpected dtype promotion in methods such as
np.polymul:This PR retains the dtype of zero array inputs.