| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
What's the benefit as opposed to just using the OO API, if you really want to specify the figure/axis? |
Sorry, something went wrong.
|
This is the opening pass at something I have been thinking about for a while. The very short version is that there is currently a major difference between 'built in' plotting (ax.foo(data, style)) and user / third-party plotting (foo(data, style, ax=ax)) and it would be better to reduce. As we do not want third-party tools to be monkey-patching methods on to Axes, we should rotate the main API to look more like functions to put everything on the same footing. The suggested API would then be def my_plotter(*data, ax, **style):
...This is bread-crumbs leading that direction. |
Sorry, something went wrong.
|
This actually looks like a reasonable argument (as much as I would like not to admit it...) |
Sorry, something went wrong.
|
Yeah, this is pretty much the same proposal from a few years ago that got
sidelined to focus on getting the data kwarg into the v1.5 release, isn't
it?
I totally get the argument, I just don't know how well I like that coding
style. Feels very basemap-ish. Whatever happened to the idea of plotting
objects?
…On Mon, Aug 28, 2017 at 11:37 AM, Antony Lee ***@***.***> wrote:
This actually looks like a reasonable argument (as much as I would like
not to admit it...)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9111 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-N7mVbidz89QregvZ__Vt6Tz1ch1ks5sct6mgaJpZM4PEATz>
.
|
Sorry, something went wrong.
|
In general I'm ok with the idea. I do think we should think about the idea of plotting objects in this context before proceeding, though. |
Sorry, something went wrong.
|
Also what's wrong with just using sca() in that case? with plt.sca(ax): ... which is probably going to be less repetitive that having to pass ax again and again. |
Sorry, something went wrong.
There was a problem hiding this comment.
If for no other reason than that this allows using the pyplot interface with an explicit axes, I'm 💯 on this.
Sorry, something went wrong.
|
I think that this and more complex objects are orthogonal. The objects are about making more complex plots easier to update and work with (ex errorbars) and this is about letting third-party code, or code that takes in not-arrays as input feel like first class citizens next to the 'official'. I expect there to be plotting functions that take in very non-array things (like a partial sql query!). It also provides a smoother path to leaving the fully implicit world to the full OO world. |
Sorry, something went wrong.
|
This is actually pass 2 at this, see #4488 |
Sorry, something went wrong.
| def test_explict_ax(): | ||
| fig, (ax1, ax2) = plt.subplots(2) | ||
| plt.plot(range(5)) | ||
| plt.plot(range(5)[::-1], ax=ax1) |
There was a problem hiding this comment.
I would just test that len(ax1.lines) == 2 instead of doing an image comp.
test name has typo ("explicit")
Sorry, something went wrong.
There was a problem hiding this comment.
There should be one line per axes (gca() is surprising! ax2 was created last so it is 'current')
Sorry, something went wrong.
There was a problem hiding this comment.
you got me :-)
but still you should be able to just test how many lines there are on each axis.
Sorry, something went wrong.
There was a problem hiding this comment.
Done
Sorry, something went wrong.
| # A gensym-like facility in case some function takes an | ||
| # argument named washold, ax, or ret | ||
| washold, ret, ax = 'washold', 'ret', 'ax' | ||
| washold, ret = 'washold', 'ret' |
There was a problem hiding this comment.
the comment above needs to be updated
side point: I think we should just throw an exception in this case -- the parameter name is part of the API so renaming it seems silly
Sorry, something went wrong.
| washold, ret = 'washold', 'ret' | ||
| bad = set(args) | {varargs, varkw} | ||
| while washold in bad or ret in bad or ax in bad: | ||
| if 'ax' is set(args): |
There was a problem hiding this comment.
I was suggesting to do the same for washold and ret below.
Sorry, something went wrong.
|
Even if this turns out to be the way to go, bringing in such a major strategic change with so little discussion and review is not good. Suggestion: leave this out of 2.1, and make it the proposed centerpiece of 2.2, with a very short release cycle--say, Nov. 1 as the target. |
Sorry, something went wrong.
|
It was worth a shot! I am taking @efiring 's comment as a veto of this going in for 2.1. Delaying to 2.2 in Nov would give us time to write some collateral around this change, flesh out some of the other implications, and retroactively write a MEP which is probably for the best |
Sorry, something went wrong.
|
Having though a bit about this, right now I belive my preferred take on such an API ("to make pyplot and external functions more symmetrical") would be with plt.sca(ax): # or a new function
plt.plot(...)
seaborn.somemethod(...)
# when sca() is *exited* there is *no* current axes,
# so plt.gca() would return None and plt.plot would error
which seems better than having to pass the same ax again and again. |
Sorry, something went wrong.
|
However this means inside of every function there must be a call to plt.gca(). The other long term goal is to get away from the shared global state of pyplot (so everything GC's reasonable, etc). Having no current figure/ax is a non-starter. pyplot (and all of it's shared global state) exists as convince methods for people sitting in an interactive shell and I do not think we will ever be able to remove it, just make it possible for people to use without it. Having a context manager that resets the current axes to what it was before would be a reasonable thing though. XXX(..., ax=ax) is not that much more onerous than ax.XXX(...) |
Sorry, something went wrong.
There was a problem hiding this comment.
In terms of code, this looks good, but the PR introduces a backward incompatible change.
On the documentation front, a lot of the docstrings need to be updated to reflect the addition of an optional keyword argument. I'm happy to push the missing documentation.
I'm also concerned about the unit tests. While indeed, this has been tested on one of the pyplot function, I think we should maybe write smoke tests coverage all pyplot functions concerned by this change.
Sorry, something went wrong.
| ax = gca() | ||
| else: | ||
| ax = args[0] | ||
| ax, = args |
There was a problem hiding this comment.
This will fail if args has more arguments than one. If args is can only be one optional argument, why not change *args into an actual optional keyword argument? That would make the code more readible, and more easily documentable than currently.
Note that because of this line we are currently introducing a backward compatible change with this PR.
Sorry, something went wrong.
| """ | ||
|
|
||
| fig = gcf() | ||
| if fig is None: |
There was a problem hiding this comment.
The docstring needs to be update to reflect the addition of an optional keyword argument.
Sorry, something went wrong.
|
|
||
|
|
||
| def box(on=None): | ||
| def box(on=None, ax=None): |
There was a problem hiding this comment.
The docstring needs to be update to reflect the addition of an optional keyword argument.
Sorry, something went wrong.
| loc : {'center', 'left', 'right'}, str, optional | ||
| Which title to set, defaults to 'center' | ||
|
|
||
| ax : matplotlib.axes.Axes, optional |
There was a problem hiding this comment.
👍
Sorry, something went wrong.
|
|
||
| """ | ||
| return gca().set_title(s, *args, **kwargs) | ||
| return _pop_or_gca(kwargs).set_title(s, *args, **kwargs) |
There was a problem hiding this comment.
The docstring needs to be update to reflect the addition of an optional keyword argument.
Sorry, something went wrong.
|
rebased to keep the dream alive. |
Sorry, something went wrong.
|
Since this Pull Request has not been updated in 60 days, it has been marked "inactive." This does not mean that it will be closed, though it may be moved to a "Draft" state. This helps maintainers prioritize their reviewing efforts. You can pick the PR back up anytime - please ping us if you need a review or guidance to move the PR forward! If you do not plan on continuing the work, please let us know so that we can either find someone to take the PR over, or close it. |
Sorry, something went wrong.
|
As a side-note: The place where the ax keyword is most present is the pandas plot API. Unfortunately, they have a different semantic (“if not given, create a new axes” vs. pyplot: “if not given, use the current axes - only if there is no current axes, create a new one). I've marked this as keep and needs comment/discussion because it really something to investigate, but the correct approach is not yet clear. |
Sorry, something went wrong.
This allows passing `ax=some_ax` or `fig=some_fig` into all of the pyplot plotting functions.
|
I could not quickly figure out how to convince the generated annotations to not use the fully qualified class names. |
Sorry, something went wrong.
Bit confused why it was not hitting these before.
|
mypy is still also a bit unhappy (it does not like forwarding returns through unconditionally...I guess the fix would be to make the generating code smart enough to drop the return if the wrapped function claims to only ever return None. |
Sorry, something went wrong.
|
This has significantly bit-rotted. I still think this is a good idea, but will close for now. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for contributing this improvement! Adding ax as an implicit input to pyplot functions looks useful for making the API more consistent. I’ll be interested to see how this behaves across different plotting functions and whether the tests cover the expected behavior. Great work!
Sorry, something went wrong.
|
@gargcodes2006 please not that this is not implemented right now. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This allows passing ax=some_ax into all of the pyplot plotting
functions.
PR Checklist