-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
interation of set_eng_float_format and pivot_tables #11981
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
not so friendly, needs a nan-check before handing off to want to do a pull-request? |
OK - I'll have a go since you've classified it as a novice level issue. Last time I tried (with a csv issue in 2014), I got lost very quickly. I'll get back to you in a week or so. cheers |
@ChristopherShort ok thanks. lmk. |
Hi, Regards, |
0.18.2 |
yadu - thanks - this has been on my conscience for a couple of months (the 1 week blew right past). I'll find something else I can contribute too. |
No worries. cheers. |
Closes pandas-dev#11981 Updated the v0.18.2 document Updated the document v0.18.2.txt and the test test_nan Updated test_nan for smoke test
EngFormatter throws an exception if passed 'inf' as below. This patch checks for infinity and just returns 'inf' in that case. xref #11981 Author: Johnny Gill <[email protected]> Closes #14214 from swfiua/master and squashes the following commits: f2348e7 [Johnny Gill] test EngFormatter with np.inf 83f4091 [Johnny Gill] add check for infinity in __call__ of EngFormatter
There appears to be an interaction between the option for float display length and pivot_table methods on integers. This issue arose when working on a dataset with both floats and integers - but this arose on operations on integers part of the dataset.
The following example throws an error from the
format.py
module.Swap the comments on the formatting options (undoing the setting for floats) and it runs fine.
In my dataset - there were no missing values following the pivot table operation and the error still occurs. In the sample code below, NaNs may be causing the formatting issue, but that didn't appear to be the case for me.
cheers
Chris
The text was updated successfully, but these errors were encountered: