BUG: improve integer step selection in MaxNLocator #7770
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
MaxNLocator with integer=True was unnecessarily restricting the possible steps. The restriction to integers is now done after scaling, not before.
dopplershift
approved these changes
Jan 9, 2017
tacaswell
approved these changes
Jan 9, 2017
tacaswell
added a commit
that referenced
this pull request
Jan 9, 2017
BUG: improve integer step selection in MaxNLocator
|
backported as 5cdf8af |
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.
MaxNLocator with integer=True was unnecessarily restricting the
possible steps. The restriction to integers is now done after
scaling, not before.