You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't reproduce this, neither on master, nor in 3.2.1.
Its hard to see why #13642 would have any effect if there were subplots or not since the scaling is independent in each axes, so I'm a little skeptical of the bisect.
Are both of you using a clean matplotlibrc? Maybe there is something in there that has a bad interaction?
This doesn't happen with plot for me (the single point doesn't show up, but the axes are autoscaled properly). I can also slim it down to a very simple example below, and the same issue persists.
I can also reproduce in master with Python 3.6.4, numpy Python 1.16.2 with Qt5Agg backend, no changes to rc file - which is a conda environment with matplotlib development version installed on top.
In case you want to look for differences, this is my `conda list` output:
OK, this is some sort of round off error. pp.get_datalim(ax.transData) gives Bbox(x0=0.0, y0=2.7755575615628914e-17, x1=0.0, y1=2.7755575615628914e-17) in my conda env and Bbox(x0=0.0, y0=0.0, x1=0.0, y1=0.0) in my development env.
Activity
dstansby commentedon Apr 21, 2020
I can bisect this back to b03370a from #13642
jklymak commentedon Apr 21, 2020
I can't reproduce this, neither on master, nor in 3.2.1.
Its hard to see why #13642 would have any effect if there were subplots or not since the scaling is independent in each axes, so I'm a little skeptical of the bisect.
Are both of you using a clean matplotlibrc? Maybe there is something in there that has a bad interaction?
Can anyone else reproduce this?
Does it happen with
plot?dstansby commentedon Apr 21, 2020
I'm using the
macosxbackend, and as far as I know a clean matplotlibrc.QuLogic commentedon Apr 21, 2020
I can reproduce with
TkAggas well, and that's the only thing set in my matplotlibrc.jklymak commentedon Apr 21, 2020
which python and numpy? I'm using
dstansby commentedon Apr 21, 2020
I'm 3.7.7 and 1.18.1
QuLogic commentedon Apr 21, 2020
My environment is always as old as possible, Python 3.6.8 and NumPy 1.15.0
jklymak commentedon Apr 21, 2020
Well, I can't reproduce, so I can't really help debug. Just upped to 3.8.2 and numpy 1.18.2 and it still works fine for me.
Qt5Aggandmacosx.dstansby commentedon Apr 21, 2020
This doesn't happen with plot for me (the single point doesn't show up, but the axes are autoscaled properly). I can also slim it down to a very simple example below, and the same issue persists.
jklymak commentedon Apr 21, 2020
I can reproduce if I use a base environment installed directly from conda. But I cannot reproduce in my dev environment.
ImportanceOfBeingErnest commentedon Apr 21, 2020
I can also reproduce in master with Python 3.6.4, numpy Python 1.16.2 with Qt5Agg backend, no changes to rc file - which is a conda environment with matplotlib development version installed on top.
In case you want to look for differences, this is my `conda list` output:
jklymak commentedon Apr 21, 2020
OK, this is some sort of round off error.
pp.get_datalim(ax.transData)givesBbox(x0=0.0, y0=2.7755575615628914e-17, x1=0.0, y1=2.7755575615628914e-17)in my conda env andBbox(x0=0.0, y0=0.0, x1=0.0, y1=0.0)in my development env.jklymak commentedon Apr 21, 2020
yields on my pure conda env:
On my dev env:
jklymak commentedon Apr 21, 2020
narrowing down further:
pure conda:
My dev env:
jklymak commentedon Apr 21, 2020
So, to me, the fundamental problem is just choosing the data lim in the face of y0 = y1
kannes commentedon Apr 27, 2020
This overwhelming and quick response was totally unexpected. Thank you guys so much!