-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
DEPR: Index.format? #55413
Comments
It's used externally. Github code search shows at least catboost uses it There are a couple others too, see |
The catboost example looks like they just vendored all of pandas. The others are look like largely matches on the word "format" which isn't using our Index.format. |
My bad, there seem to be a lot of false positives from Github code search. I think this one is an actual usage (not that it's a widely used project, just pointing out the existence of code that uses format) |
At any rate, I don't really care too much if this is deprecated, though. |
cc @attack68 |
This is used in one place in Styler rendering internally. This is code that predates me, but it's used to be able to get positions in an index so that Styler can display sparsified output.
|
@attack - just in case you missed it, this is from the OP
So I take it you have no objection to making it internal. |
I would expect |
no objection at all to the refactor |
Does anyone actually use this? Internally we use it for some html/latex rendering but we don't use most of the keywords so it would be simpler to refactor to use a private method for those.
I've been trying to unravel the various EA formatting methods to try to use the same patterns everywhere, align keywords, etc. Doing this for Index.format wouldn't be that hard, but it would be easier to just deprecate it if it isn't used externally.
The text was updated successfully, but these errors were encountered: