Add get/set_in_layout to artist API docs. #13436
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
They don't seem to fit in any existing subsection and creating a section just for them seems silly, so move them, together with other single-entry subsections, to "misc.". To compensate the loss of the "margins and autoscaling subsection", add mention of autoscaling in the first line of the sticky_edges docstring, to keep that term ctrl-f'able on the API docs page.
jklymak
approved these changes
Feb 14, 2019
ImportanceOfBeingErnest
approved these changes
Feb 14, 2019
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Feb 14, 2019
timhoffm
added a commit
that referenced
this pull request
Feb 14, 2019
…436-on-v3.0.x Backport PR #13436 on branch v3.0.x (Add get/set_in_layout to artist API docs.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They don't seem to fit in any existing subsection and creating a section
just for them seems silly, so move them, together with other
single-entry subsections, to "misc.".
To compensate the loss of the "margins and autoscaling subsection", add
mention of autoscaling in the first line of the sticky_edges docstring,
to keep that term ctrl-f'able on the API docs page.
noticed while reviewing #13432.
PR Summary
PR Checklist