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
Python 3.5 NumPy 1.10.0 rounding (issue?) #7355
Comments
It's a discrepancy in
Still arguably a bug -- notice that it's only the float64 scalar type that's affected; the array printer works correctly:
|
The |
See #6136 too. |
I think this is a duplicate of #6136. One of these should be closed. The other should be renamed: string representation of floating point numbers in arrays should not display extra digits. Simpler test case:
First one should be "[0.12345678]". Second one should be "[0.123456789012345678]". |
prints distinguishing parentheses for scalar types addresses issue numpy#7355, numpy#7913, related to numpy#6908
I think this one is no longer an issue |
Thanks @ron819, indeed fixed. |
It's just how arrays are printed. The printing precision can be set, but by default it isn't large in order that more array elements may be displayed. The value is fine.
|
@charris better to open a new ticket this one is very old |
Not sure if this is a bug or there is simply a discrepancy between NumPy and Python. Though this is what I am seeing in some (not all) cases. FYI, similar (but not the exact same) behavior for
np.float128
.The text was updated successfully, but these errors were encountered: