Improve docstring of Axes.pcolormesh #11344
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
e400bf7 to
f6f9149
Compare
|
I have no idea what the policy is on backporting |
|
I think @tacaswell said that we can backport doc changes to 2.2.3 so long as someone actually shepherds it. I personally find that somewhat confusing because I don't understand what 2.2.x-doc is for in that case, but I'll leave the release packaging to the pros. |
QuLogic
added a commit
that referenced
this pull request
Jun 1, 2018
…n-v2.2.x Backport PR #11344 on branch v2.2.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
As part of #10148: Docstring update for
Axes.pcolormesh.The
Parameterssection is almost identical to the one inAxes.pcolorfrom #11317. The only difference for that section is the additionalshadingparameter.