BUG: DataFrame.style displays wrong value for long integers #52272 FIX #52686
Conversation
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
mroeschke
reviewed
Apr 17, 2023
doc/source/whatsnew/v2.1.0.rst
Outdated
| @@ -305,6 +305,8 @@ Conversion | |||
| ^^^^^^^^^^ | |||
| - Bug in :meth:`ArrowDtype.numpy_dtype` returning nanosecond units for non-nanosecond ``pyarrow.timestamp`` and ``pyarrow.duration`` types (:issue:`51800`) | |||
| - Bug in :meth:`DataFrame.info` raising ``ValueError`` when ``use_numba`` is set (:issue:`51922`) | |||
| - Bug in :func:`_default_formatter`, If the DataFrame contains integers with more digits than can be represented by floating point double precision | |||
There was a problem hiding this comment.
Suggested change
| - Bug in :func:`_default_formatter`, If the DataFrame contains integers with more digits than can be represented by floating point double precision | |
| - Bug in :func:`DataFrame.style.to_latex` and :func:`DataFrame.style.to_html` if the DataFrame contains integers with more digits than can be represented by floating point double precision (:issue:`52272`) |
mroeschke
reviewed
Apr 17, 2023
doc/source/whatsnew/v2.1.0.rst
Outdated
| @@ -305,6 +305,8 @@ Conversion | |||
| ^^^^^^^^^^ | |||
| - Bug in :meth:`ArrowDtype.numpy_dtype` returning nanosecond units for non-nanosecond ``pyarrow.timestamp`` and ``pyarrow.duration`` types (:issue:`51800`) | |||
| - Bug in :meth:`DataFrame.info` raising ``ValueError`` when ``use_numba`` is set (:issue:`51922`) | |||
| - Bug in :func:`_default_formatter`, If the DataFrame contains integers with more digits than can be represented by floating point double precision | |||
| _default_formatter returns incorrect data value truncated due to loss of precision. Fix adds to html or latex as string in this case (:issue:`52272`) | |||
There was a problem hiding this comment.
Suggested change
| _default_formatter returns incorrect data value truncated due to loss of precision. Fix adds to html or latex as string in this case (:issue:`52272`) |
mroeschke
reviewed
Apr 17, 2023
…v#52272 FIX documentation and tests
mroeschke
approved these changes
Apr 18, 2023
|
Thanks @lusolorz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
doc/source/whatsnew/v2.1.0.rstfileFix Description: Returns string if value exceeds float point double to avoid loss of precision.