-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
MAINT: Adjust type promotion in linalg.norm #10368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I added the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks all OK to me
But the failures of course suggest there is a problem... |
Failures are caused by #10374 |
b61ec46
to
bdf226c
Compare
numpy/linalg/linalg.py
Outdated
@@ -24,7 +24,7 @@ | |||
add, multiply, sqrt, maximum, fastCopyAndTranspose, sum, isfinite, size, | |||
finfo, errstate, geterrobj, longdouble, moveaxis, amin, amax, product, abs, | |||
broadcast, atleast_2d, intp, asanyarray, object_, ones, matmul, | |||
swapaxes, divide, count_nonzero | |||
swapaxes, divide, count_nonzero, reciprocal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't need reciprocal any more...
Apart from the nitpick, would seem ready to go in. |
…r speed Fixes numpygh-10364, partly by adjusting the promise in the release notes
Updated with the nit fix |
bdf226c
to
04896b0
Compare
OK, will merge now. |
Needs a forward port, which can be done through the GitHub UI alone |
Relates to #10364.
Unfortunately the failing case there still doesn't work when the result is a scalar, due to falling afoul of #10322. We fix this by just not making any promise about the scalar case.
That seems pretty reasonable to me, since numpy makes it very hard to keep float32 scalars around anyway.