Hello,
I am experiencing strange behavior using mpl_toolkits.basemap.Basemap.
My understanding is that pcolormesh is faster than pcolor, and thus
preferable. Here is a minimal example (below) where I get a different
plot from pcolormesh than from pcolor.
On two systems (mac os x 10.9.5; Ubuntu 1
Final update.
I've done some more searching, and found a couple more things. It seems
that this problem occurs with the backend set to "Agg"
(`matplotlib.use("agg")), so it isn't related to the interactive backends.
In addition, the problem does not occur with a random Polygon object added
to an a
Update 2.
I made a new Anaconda Python 2.7 environment and cycled through some
different MPL versions. Everything works as I would expect in 1.4.0;
however, moving to 1.4.1 is when the problem occurs. I see this same
problem if I do the OO commands instead of pyplot.
import numpy as np
import mat
Update.
This is a problem also in Anaconda Py3.4 with MPL 1.4.2, but it works
without a problem on MPL 1.4.0.
Ryan
On Mon, Dec 8, 2014 at 12:15 PM, Ryan Nelson wrote:
> Hello all,
>
> I'm having an issue with fill_between. It seems that setting the keyword
> `linewidth=0` removes the entire pa
zypper ~ apt-get
It did install binaries from a Novell repository.
I checked for previous installed and I could not find anything.
cheers
--
View this message in context:
http://matplotlib.1069221.n5.nabble.com/error-import-matplotlib-pyplot-tp44297p44572.html
Sent from the matplotlib - users
Hello all,
I'm having an issue with fill_between. It seems that setting the keyword
`linewidth=0` removes the entire patch, rather than the just the bounding
lines. Example:
import numpy as np
import matplotlib.pyplot as plt
x = np.linspace(0, 2*np.pi, 1000)
y = np.sin(x)
plt.fill_between(
