oki sorry for griddata it was my fault. After the mail on the list, I cleaned
all precedent installation and now it's working fine with numpy...
Thanks,
N.
Le samedi 10 juin 2006 13:45, Jeff Whitaker a écrit :
> Eric Firing wrote:
> > Thanks. There were in fact several points of incompatibil
Eric Firing wrote:
> Thanks. There were in fact several points of incompatibility with
> Numeric and numarray. (Normally I would have checked this, but I
> slipped up.) I have changed quiver.py and numerix to solve the
> immediate problem, and to slightly reduce the incidence of such
> problem
> "humufr" == humufr <[EMAIL PROTECTED]> writes:
humufr> "should" but sometimes perhaps it's too hard to do
humufr> this. One solution, if the function won't work with
humufr> anything else than numpy, is to print a warning/error
humufr> message for this specific function. Tha
Le vendredi 9 juin 2006 18:30, Christopher Barker a écrit :
> [EMAIL PROTECTED] wrote:
>
> well, anyone using Numeric (or numarray), can just keep on using it for
> a god while. So something that works now should work for a while into
> the future.
"should" but sometimes perhaps it's too hard to d
Thanks. There were in fact several points of incompatibility with
Numeric and numarray. (Normally I would have checked this, but I slipped
up.) I have changed quiver.py and numerix to solve the immediate
problem, and to slightly reduce the incidence of such problems in the
future. The real so
[EMAIL PROTECTED] wrote:
> I think that we will have soon a big problem with the scientific soft in
> python. Some of them will use numpy, Numeric or numarray and they will be
> totally incompatible.
I understand and to some extent share, your frustration, but the problem
already existed with
Hi,
just to tell that the new quiver2 sample are not working with numarray.
/usr/lib/python2.4/site-packages/matplotlib/quiver.py", line 237, in
_make_verts
scale = nx.amax(a) * math.sqrt(len(a)) # crude auto-scaling
AttributeError: 'module' object has no attribute 'amax'
