Repository navigation
DOC: clarify that clim is not a valid kwarg if vmin/vmax are used - #10354
Merged
Merged
Conversation
Member
Author
|
Now reads:
|
dstansby
approved these changes
Jan 31, 2018
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
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
Closes #10346
@heath730 noted that
climis listed as aQuadMeshkwarg, but calling inpcolormeshis ignored in favour ofvmin/vmax. This just edits theScalarMappable.set_clim()docstring, which is mapped downstream to methods that callScalarMappableto make this clear.As discussed in #10346, its a bit strange to pass all the
set_blahstrings downstream; some of them make no sense, and some have no effect. This is probably a bigger issue that will need some thought (after traitlets??)