Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DOC: add more cross-ref and explanatory image #25109

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

Merged
merged 1 commit into from
Feb 13, 2023

Conversation

jklymak
Copy link
Member

@jklymak jklymak commented Jan 30, 2023

PR Summary

This adds a bit more cross referencing to figure. Also improves figures.rst by adding an image showing backends in action ...

FigureTypes

PR Checklist

Documentation and Tests

  • Has pytest style unit tests (and pytest passes)
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • New plotting related features are documented with examples.

Release Notes

  • New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
  • API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
  • Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst

@jklymak jklymak force-pushed the doc-figure-cross-ref branch 2 times, most recently from 2a272e1 to 888e90f Compare January 30, 2023 20:24
@jklymak
Copy link
Member Author

jklymak commented Jan 30, 2023

@jklymak jklymak force-pushed the doc-figure-cross-ref branch from 888e90f to 7569a5e Compare January 30, 2023 21:10
@jklymak
Copy link
Member Author

jklymak commented Feb 10, 2023

I'll ping for a review on this. I think the image is helpful - if someone wants to add a different image later that they think is more helpful, that is fine. The standard for doc changes is not "is this exactly what I would do?" but rather "is this an improvement?".

@jklymak jklymak force-pushed the doc-figure-cross-ref branch from 7569a5e to 88486b3 Compare February 11, 2023 23:54
Copy link
Member

@story645 story645 left a comment

Choose a reason for hiding this comment

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

I'm not blocking on the figure, but I'm concerned that it'll be confusing in a way where it's not an improvement.

@@ -39,7 +49,15 @@ that renders Notebooks (PyCharm, VSCode, etc), then they have a backend that
will render the Matplotlib Figure when a code cell is executed. One thing to
be aware of is that the default Jupyter backend (``%matplotlib inline``) will
by default trim or expand the figure size to have a tight box around Artists
added to the Figure (see :ref:`saving_figures`, below).
added to the Figure (see :ref:`saving_figures`, below). If you use one of the
non-default backends you will likely need to use an ipython "magic" like
Copy link
Member

Choose a reason for hiding this comment

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

can you add a link to the list of default backends here?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure what list of "default backends" you are referring to?

Copy link
Member

Choose a reason for hiding this comment

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

I was thinking our backend list but you're specifically talking about the default Jupyter backend here so scratch that comment and maybe instead state jupyter inline (default) backend

@jklymak jklymak force-pushed the doc-figure-cross-ref branch 3 times, most recently from f704164 to 951d148 Compare February 12, 2023 21:27
@jklymak
Copy link
Member Author

jklymak commented Feb 12, 2023

@story645
Copy link
Member

story645 commented Feb 12, 2023

Oh that's so much better! I like it a lot. :)

@jklymak jklymak force-pushed the doc-figure-cross-ref branch from 951d148 to 432b60e Compare February 13, 2023 00:38
Copy link
Member

@story645 story645 left a comment

Choose a reason for hiding this comment

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

Wording/alt text nits that I can put in a follow up so you can self merge w/ or w/o them.

@@ -39,7 +49,15 @@ that renders Notebooks (PyCharm, VSCode, etc), then they have a backend that
will render the Matplotlib Figure when a code cell is executed. One thing to
be aware of is that the default Jupyter backend (``%matplotlib inline``) will
by default trim or expand the figure size to have a tight box around Artists
added to the Figure (see :ref:`saving_figures`, below).
added to the Figure (see :ref:`saving_figures`, below). If you use one of the
non-default backends you will likely need to use an ipython "magic" like
Copy link
Member

Choose a reason for hiding this comment

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

I was thinking our backend list but you're specifically talking about the default Jupyter backend here so scratch that comment and maybe instead state jupyter inline (default) backend

@jklymak jklymak force-pushed the doc-figure-cross-ref branch from 432b60e to 4f12d48 Compare February 13, 2023 16:21
@story645 story645 added this to the v3.7-doc milestone Feb 13, 2023
@story645 story645 merged commit 76dd07e into matplotlib:main Feb 13, 2023
@jklymak
Copy link
Member Author

jklymak commented Feb 14, 2023

@meeseeksdev backport to v3.7.0-doc

@jklymak jklymak deleted the doc-figure-cross-ref branch February 14, 2023 17:03
@lumberbot-app
Copy link

lumberbot-app bot commented Feb 14, 2023

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.7.0-doc
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 76dd07e529b2bc5169ac7867b85cf8bc783a9460
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #25109: DOC: add more cross-ref and explanatory image'
  1. Push to a named branch:
git push YOURFORK v3.7.0-doc:auto-backport-of-pr-25109-on-v3.7.0-doc
  1. Create a PR against branch v3.7.0-doc, I would have named this PR:

"Backport PR #25109 on branch v3.7.0-doc (DOC: add more cross-ref and explanatory image)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

jklymak pushed a commit to jklymak/matplotlib that referenced this pull request Feb 14, 2023
DOC: add more cross-ref and explanatory image
(cherry picked from commit 76dd07e)
jklymak added a commit to jklymak/matplotlib that referenced this pull request Feb 14, 2023
jklymak added a commit that referenced this pull request Feb 20, 2023
* Merge pull request #25109 from jklymak/doc-figure-cross-ref

DOC: add more cross-ref and explanatory image
(cherry picked from commit 76dd07e)

* Backport PR #25109: DOC: add more cross-ref and explanatory image

---------

Co-authored-by: hannah <[email protected]>
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.

3 participants