Michael Droettboom wrote:
> David Huard wrote:
>> Hi,
>>
>> calling show returns the following error using the numpy maskedarray
>> branch. The figure is a quiver plot on a basemap instance.
>
> I haven't personally done any testing with the maskedarray branch
> myself, though I know Eric Firing
David Huard wrote:
> Hi,
>
> calling show returns the following error using the numpy maskedarray
> branch. The figure is a quiver plot on a basemap instance.
I haven't personally done any testing with the maskedarray branch
myself, though I know Eric Firing has done a little.
> /usr/local/lib
Hi,
calling show returns the following error using the numpy maskedarray branch.
The figure is a quiver plot on a basemap instance.
/usr/local/lib64/python2.5/site-packages/matplotlib/figure.pyc in draw(self,
renderer)
696
697 # render the axes
--> 698 for a in self.axes:
Michael Droettboom skrev:
> Interesting.
>
> Perhaps anything that throws an exception in the FT2Font constructor
> (which a bad font or a missing font would both do), is throwing off the
> reference count for the object and failing that assertion, rather than
> passing the exception back to Py
Interesting.
Perhaps anything that throws an exception in the FT2Font constructor
(which a bad font or a missing font would both do), is throwing off the
reference count for the object and failing that assertion, rather than
passing the exception back to Python. Only a theory.
What version of
Michael Droettboom skrev:
It's possible -- the version of freetype in the win32_static.tar.gz
package is 2.1.7. I have 2.1.9 on my (working) Linux box. Perhaps
something between those point releases fixes this bug. But it could be
a lot of other things, too.
I'm going to file a bug for thi
Yep. I fixed that bug in the wrong way -- it needs to ignore existing
limits on the first line, and then subsequently not ignore. I think I
have it working now with both your old example and this one. (r4890)
Cheers,
Mike
Darren Dale wrote:
> I noticed another bug:
>
> l1,=plot([1,2,3,4])
>
I noticed another bug:
l1,=plot([1,2,3,4])
l2,=plot([2,3,4,5])
l1.set_ydata([3,4,5,6])
l2.set_ydata([5,6,7,8])
gca().relim()
gca().autoscale_view()
draw()
This sets the y limits to 5 and 8, rather than 3 and 8. Even if I change only
the ydata for l1, the limits are still calculated according to
It's possible -- the version of freetype in the win32_static.tar.gz
package is 2.1.7. I have 2.1.9 on my (working) Linux box. Perhaps
something between those point releases fixes this bug. But it could be
a lot of other things, too.
I'm going to file a bug for this so it doesn't get lost.
C
