Skip to content

Clarify that it is ok to use plt.subplots to create figures #19554

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

Closed
wants to merge 1 commit into from

Conversation

ianhi
Copy link
Contributor

@ianhi ianhi commented Feb 21, 2021

PR Summary

Adds a line explaining that it is ok to use pyplot methods to create figures. This was (is perhaps) confusing for me and seems to be for other users as well https://discourse.matplotlib.org/t/how-do-i-use-the-object-oriented-interface-without-having-to-rely-on-pyplot/21877

cc @jklymak because this is based on your response to that discourse post.

PR Checklist

  • Documentation is sphinx and numpydoc compliant (the docs should build without error).

This is a real source of confusion for users when told that they should prefer the OO style.
@@ -41,7 +41,8 @@
.. note::

In general, try to use the object-oriented interface over the pyplot
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In general, try to use the object-oriented interface over the pyplot
In general, the explicit interface is preferred over the pyplot

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would require rephrasing the earlier paragraphs in the tutorial as well. That may be a good thing to do but wasn't my intention here. Is this enough of an incremental improvement to stand on its own?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

explicit object-oriented..?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's better but it is still a break from how the opening paragraph describes things. But perhaps Im worrying too much about that

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe fix the first parapraph while we are here? It is not terribly clear.

Comment on lines +44 to +45
interface for making the plots. However, for creating figures and axes
the pyplot interface with `~.pyplot.subplots` should be preferred.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
interface for making the plots. However, for creating figures and axes
the pyplot interface with `~.pyplot.subplots` should be preferred.
interface for making the plots. The `~.pyplot` module still has some useful
shortcuts, and in particular is the preferable method for instantiating figures
and axes via ``fig=plt.figure()`` or ``fig, axs=plt.subplots(2, 1)``.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this.

@jklymak
Copy link
Member

jklymak commented Feb 21, 2021

Maybe something like the above? Or even more detail. There is lots of good stuff in pyplot that this note was not meant to forbid. ie. plt.rcParams is pretty helpful, rather than importing matplotlib.

@jklymak jklymak marked this pull request as draft February 26, 2021 21:11
@jklymak
Copy link
Member

jklymak commented Mar 21, 2021

@ianhi are you coming back to this?

Copy link

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.

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Nov 17, 2023
@rcomer
Copy link
Member

rcomer commented Nov 17, 2023

This section had a bit of a re-write at #22613 and the relevant note now says "...for plotting". Is there more to do here?

@timhoffm
Copy link
Member

Wecshiuld align with #26388, which is sort of orthogonal but would need a rewrite of the same sections. I‘d be ok with closing here.

@github-actions github-actions bot removed the status: inactive Marked by the “Stale” Github Action label Nov 20, 2023
@rcomer rcomer closed this Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants