Changing the axis title

[jwhendy]

Hello,

I'm coming from R + ggplot2 and I'm not sure what I'm doing wrong here to change the axis title.

from plotnine import *
from plotnine.data import *
p = ggplot(aes(x='displ', y='cty'), mpg) + scale_x_continuous(name="foo")
p + geom_point()

From the docs

class plotnine.scales.scale_x_continuous(**kwargs)
name (str, optional) -- Name used as the label of the scale. This is what shows up as the axis label or legend title.

---

R equivalent:

library(ggplot2)
data(mtcars)

ggplot(mtcars, aes(x=disp, y=mpg)) + geom_point() + scale_x_continuous(name="foo")

Thanks for taking a look, and sorry if I've misunderstood due to being new to plotnine.

[jwhendy]

Maybe should have looked at the code first. I'm also kind of new to python, but it sort of looks to me like this might not be implemented. The scale class seems to set name=None.

[has2k1]

The name parameter works for naming the titles to the guides of other scales, but it is ignored for the x and y axis titles.

[jwhendy]

Installed from master.Tried with both scale_x_continuous and scale_y_continuous and name='foo' works like a champ. Thanks!

[jwhendy]

Update: when I use ggplot2, I'll frequently do scale_y_continuous("") when the label is obvious or unhelpful.

I just found that passing an empty string reverts to whatever the column label is. In other words, name='foo' works, but not name=''. I can pass a space to hack this, but wanted to bring it up.

Taking an empty string would match ggplot2 behavior to remove an axis label.

[jwhendy]

It looks like you also now allow name='', which is awesome.

Any estimate on this getting pushed to PyPI? I just got a new computer and used pip install plotnine, having forgotten about this issue. I had to re-discover that the name option isn't working on the released version and would guess other users will run into the same.

[has2k1]

There are a few issues with the documentation and examples I hoped to sort out before a release. As there are many improvements in master, I think I'll try to make a release in a few days.

[jwhendy]

Are these all in issues? I've been using R's ggplot2 for maybe 7 years and the fact that you've built it for python is about the coolest thing ever. I've putzed with some other libraries, but when I just need to get something done, I use this!

tl;dr version: do you need help with some of these things? I can certainly write up some examples. For example I noticed there aren't any for geom_text() and annotate() yesterday...

If you have an overall strategy (for example, "Replicate R's ggplot2 pages over time"), I will happily help out.

[has2k1]

Are these all in issues?

Some of them are about the doc infrastructure.

If you have an overall strategy (for example, "Replicate R's ggplot2 pages over time"), I will happily help out
The goal is for examples use the geoms (and the rest) as:

1. Part of a data analysis narrative especially the graphical exploration part.
2. In an elaborate visualisation to show off the gallery.

However, this criteria is not good for the short term. I did not want to just replicate the examples from ggplot2; we have a similar API and so the examples are easily transferable, but this thinking is slightly biased towards people are somewhat familiar with R.

I appreciate any helping out, my vision for the documentation may not be realistic and after the next release I'll start compromising.