-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
enh: api cleanup... tostring, to_string, to_html, etc. #577
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
It might be a bit too late to remove underscores from a host of methods. I find the underscores easier on the eyes, though. For example:
looks much better to me than
but that may be largely a function of having used that convention for a long time. I agree that the API should be made uniform and consistent across the data structures. Feel free to hack away-- I'm not going to be able to invest much in this relative to the feature queue for a while |
As reference, with a little bit of pandas code i created an overview of available methods (0.8.0.dev-de6318e).
|
Very useful and interesting! |
@lodagro can you update this? would be interesting now that objects are combined |
Update? Do you mean regenerate the above table for master? |
yep...that's what I meant |
@lodagro can u also put the code u used to create it in a gist? we could make it into a script ... |
Could not find back the code i used to generate the above table, i probably did it interactively using IPython. Its not much really, on request i made a gist. The output is a html file. |
Dunno whether it's worth opening a new issue, but I would suggest that it might be worth adopting a convention like |
Also, I agree that underscores are better - what the hell is a camelCase would also be ok, it's much clearer than no word definition, and it's shorter than underscores. Re: "a bit too late". Wouldn't it be easy enough to just make aliases for each method, and raise warnings when they're called, noting that they're deprecated? Those aliases could be removed later (and the warnings could state which version they will be removed in). |
Closing -- please open issues addressing specific existing inconsistencies. |
There is a lot of semi-duplication / differences in the
Series()
andDataFrame()
methods.Maybe it's worth taking a look through them and regularising.
Fwiw, I prefer
tostring
vs.to_string
Also, would be nice to have
tohtml
on things, though expanding it is beyond the scope of this.The text was updated successfully, but these errors were encountered: