-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
np.rint(-0.0) wrong on Windows32 #7004
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
Comments
What version of numpy are you using? |
Numpy 1.10.1. |
Maybe related to this : #6685 - can you upgrade to 1.10.2? |
I see. This would likely fix it, indeed. Since I'm using conda, I'll wait for the updated release on the Anaconda channels. Thank you! |
Should this bug and that one both be closed then, or...?
|
Perhaps someone with knowledge to build Numpy on a Windows box could test? :-) |
I suspect an upgrade might do it. I don't see this bug on my Windows32 machine.
|
Closing. Please reopen if the issue is still valid in 1.11 |
np.rint(-0.0)
correctly returns-0.0
on Linux and Windows64, but not on Windows32:The text was updated successfully, but these errors were encountered: