-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
autoscale differences between 1.5.1 and 2.0.0b3 #6968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Release critical
For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Milestone
Comments
jenshnielsen
added a commit
to jenshnielsen/matplotlib
that referenced
this issue
Sep 4, 2016
jenshnielsen
added a commit
to jenshnielsen/matplotlib
that referenced
this issue
Sep 4, 2016
jenshnielsen
added a commit
to jenshnielsen/matplotlib
that referenced
this issue
Sep 4, 2016
@LevN0 in answer to your question, with v2.x if you start with mpl.rcParams['axes.autolimit_mode'] = 'round_numbers'
mpl.rcParams['axes.xmargin'] = 0
mpl.rcParams['axes.ymargin'] = 0 |
efiring
added a commit
to efiring/matplotlib
that referenced
this issue
Nov 14, 2016
dopplershift
added a commit
that referenced
this issue
Nov 14, 2016
[MRG+1] BUG: make autoscale('tight') set margins to zero; closes #6968
Closed in #7458 |
@efiring Thank you. I tried axes.autolimit_mode and it seems to result in the MPL 1.5 behavior for that aspect recovered. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Release critical
For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Based on description of tight ("If True, set view limits to data limits"), I would have expected MPL 1.5.1 behavior (see code and image below). Though perhaps there was a little margin added intentionally?
Edit: I see this first part was intended, as change #5583. See second issue below.
Aside from this, MPL 1.x use to conveniently adjust view limits for log and symlog when tight autoscaling was not on, but MPL 2 does not seem to do this anymore.
This actually also looks like a result of #5583. I would argue the previous behavior was actually desirable in many instances. Is there a way to recover it?
Python 2.7 and 3.4
Using tkagg backend.
Windows 7
The text was updated successfully, but these errors were encountered: