-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Deprecating the trellis rplot module #3445
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
@cpcloud doc-man? |
Sure! Good a time as any to learn this dark corner of pandas :) |
rplot is really useful (and I ported it back to an earlier release because I wanted to use it for a project) but it's slow, somewhat visually unappealing, and (at least for me) hard to figure out how to tweak. What if we split off visualization into a separate library that pandas would keep as a dep (i.e., the plotting module would provide Alternatively, I get the sense that rplot was trying to bring in some of the concepts that the |
or even if we didn't split it off, just give a few people the responsibility for focusing on pandas visualizations and emphasizing making them look good. |
I think it would make sense to split most of the plotting (from pandas and statsmodels) off into two projects (one ggplot-codeing-style like, one matplotlib-coding-style like). There are currently so many (matplotlib-based and otherwise -> JS, d3,...) python plotting libs showing up, it looks like some consolidation would be nice to not waste so much effort... |
Plus right now you can drop in rplot as far back as 0.11 and it'll work, so |
ggplot2 does indeed have very strong support for faceting so if this was available elsewhere rplot is Anyway, as I said elsewhere, my view is that pandas shouldn't focus on viz if a suitable alternative emerges. |
I looked around, there a bunch of libraries at this point, many of which use pandas internally (e.g., seaborn) so I don't really think it makes sense to go start something new. It would be nice to standardize on one or two though. |
Coming back to this older thread (as there was a discussion on the docs of it in #8351): I think it is a good time to reconsider the status of the trellis plotting interface in pandas (tools/rplot.py) and the arguments made above:
So: would deprecating the trellis rplot interface in pandas make sense? @orbitfold You are the original author of this I think. What is your opinion on this? As proposed by @TomAugspurger in #8351, we could make a doc section showing for each example of the current pandas trellis interface, how to do the equivalent using python-ggplot and/or seaborn for easy transitioning. |
I think you summed up the current situation pretty well: seaborn has trellis plots and it seems that much of the work on "matplotlib style higher plotting functions" is going into that library. As someone looked into how much this interface is actually used? SO? |
SO search on "[pandas] rplot" gives one question (and one answer to another question): http://stackoverflow.com/search?q=[pandas]+rplot (and other similar searches did no yield more) |
older thread but anybody for killing trellis plotting in 0.16.0 and just pointing to seaborn? |
We should at least start warning / deprecating. |
yes let's do that at least (maybe a nice box at the top of the section) |
@TomAugspurger Did you already have some examples of how to do it in seaborn? I vaguely can remember you posted it once in an issue? |
Started with a deprecation warning in #9357 |
@jorisvandenbossche I've added a bugreport in ggplot, but I think currently we are nto ready yet (faceting and categorical are not so nice in ggplot currently ...) |
Closed by #9357 |
Original title: rplot.rst needs cleaning up
http://pandas.pydata.org/pandas-docs/dev/rplot.html
plot style, dimensions, grids, legend.
The text was updated successfully, but these errors were encountered: