-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
HTML styling set_precision should take subset #11656
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
yep seems reasonable to me.. pull-requests are welcome! |
set_precision
should take subset
This is a good addition, but might be a bit of work. Right now we {% if c.value is number %}
{{c.value|round(precision)}}
{% else %}
{{c.value}}
{% endif %} c is a dict with {'type', 'value', 'class', 'props', 'selector' |
I can take this, although I'll probably require some help as I've never looked at the |
That'd be great if you want to take it. We're releasing Right now |
Ok, yeah this certainly won't make it to 0.17.1 in that case. Any thoughts on how the precision would be applied to the |
I'd say leave index alone, at least to start with. That is all going to get an overhaul before the next release when we add support for styling Indexes. |
this method is depecated and solutions are now available with Styler.format(precision) |
There's a problem in the way
.set_precision
currently works as it is being applied to all table cells indiscriminately. For instance a dataframe with means and standard errors cross validated across some parameter values theset_precision
will easily hide a lot of detail in the results.The second parameter (2nd index) is not all zeros, they're just values in the range
[1e-4, 1e-3]
. Also while for themean
columns a precision of 2 is fine, for the standard error 4 might be more appropriate. So having asubset=
keyword argument also for.set_precision
would be great.code for making the df
The text was updated successfully, but these errors were encountered: