-
Notifications
You must be signed in to change notification settings - Fork 473
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
np.isfinite() changes internal type? #481
Comments
Related to #479 . Probably the same cause; set a breakpoint at |
I think you are right, this was done to enable numpy operations working transparently on Pint Quantities. The problem is, I think, that we do know who is asking for that attribute. Everything is fine if:
However if dimensionality is importante (like I guess that if we remove the inplace conversion then |
Revisit after #905 |
I would rather add a test and close this issue. A test will always make us remember |
... which is what #925 is about. I only realized this after posting, though |
:-D Indeed. I am closing this as I am trying to keep the Issue Tracker free of polution (which good but not perfect yet results) |
Thanks for pointing this out! |
I have no idea what's going on here:
Outputs:
Why on earth does calling a numpy function modify the Quantity in-place???
The reason this even matters is because this works:
while this:
gives me a traceback (due to NumPy not implementing
__format__
):The text was updated successfully, but these errors were encountered: