Repository navigation
Make nonposy='clip' default for log scale y-axes - #2147
Merged
dmcdougall merged 1 commit intoAug 18, 2013
Merged
dmcdougall merged 1 commit into
dmcdougall merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Seems uncontroversial. We should probably make the analogous change for x so it also works for horizontal error plots. |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
|
Done and squashed. Thanks @mdboom. |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
|
Wow, that post-refactor rebase was incredibly painful. |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
LGTM 👍 |
Sorry, something went wrong.
dmcdougall
added a commit
that referenced
this pull request
Aug 18, 2013
Make nonposy='clip' default for log scale y-axes
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.
Fixes #163.
I didn't want to target 1.3.x because it's a behaviour change. Is this solution acceptable? If so, I'll add a note to api_changes.rst.