easiest thing is just to check out the svn branch here:
>
> http://matplotlib.svn.sf.net/svnroot/matplotlib/branches/v0_91_maint
>
> But for those not doing that, I think a new release is in order, but I'm
> not the one who normally makes those calls etc.
>
> Cheers,
>
>
>
> > 2) Use:
> > F.savefig(open(path, "w"), dpi=dpi)
> This is exactly what matplotlib the *Agg backends do on the 0.91.x
> maintenance branch and the trunk. Unfortunately, 0.91.2 (the latest
> release) still has this bug. This may be reason enough to push out a
> new maintenance release of 0.
2008/1/29, Neil Crighton <[EMAIL PROTECTED]>:
>
> I think it would be a shame to lose the current matplotlib 3d plotting
> functionality, even if it's not ideal. I've found it very useful for
> plotting small sets of data, and much more straightforward to use than
> Mayavi or other vtk-based 3d pl
> Thanks for the update, I'll try it tuesday from work, but I don't think
> it will change anything. I'll post some pictures/data if you want.
> What I'm passing as argument for c is a numpy array of dimension (N, 3)
> with floats between 0 and 1. When I get rid of the check at line 3777, I
> can
This is done (with corresponding simplification of the code and improved
error checking and reporting), and I have made slight changes to
scatter, but there is still an ambiguity in scatter's argument handling.
It was and is resolved in favor of treating the c argument as an array
rather than a
I don't quite understand: what kind of "c" are you passing in, what is
the original code doing with it, and what should it do with it? (I find
both the original and the suggested code hard to understand, which makes
me think that neither is actually what we want.)
c is a named argument of th
Hi,
I'm trying to display a scatter plot in 3D, and it calls the 2D scatter
plot, in axes.py. This method tests for validity of the color argument in
line 3777 :
if not is_string_like(c) and iterable(c) and len(c)==len(x):
colors = None
else:
colors = ( colorC
