Guido van Rossum wrote:
> > I would propose the following for multi-dimensional arrays:
> >
> > a = array.array('d', 20000, 20000)
> >
> > or:
> >
> > a = array.xarray('d', 20000, 20000)
>
> I just realized that multi-dimensional __getitem__ shouldn't be a big
> deal. The question is, given the above declaration, what a[0] should
> return: the same as a[0, 0] or a copy of a[0, 0:20000] or a reference
> to a[0, 0:20000].
Or a …
[View More]ValueError? In the face of ambiguity, refuse the temptation to
guess.
IIRC, this issue caused lots of problems in the numpy world. cc'ing Paul
in case he wants to jump in to fill in my rusty memory.
Why does submitting a patch to arraymodule seem an easier path than
modifying numarray or numpy to support what's needed? I believe that
the goals of numarray aren't that different from what Scott is trying to
do (memory management APIs, etc.).
I'd like to see fewer multi-dimensional array objects, not more...
--david ascher
[View Less]
Howdy:
Shoudln't line 296 in MLab.py of Numeric 21.0, which currently reads:
val = squeeze(dot(transpose(m)*conjugate(y)) / fact)
read:
val = squeeze(dot(transpose(m),conjugate(y)) / fact)
Thanks,
D.Kelson
Carnegie Observatories
http://www.ociw.edu/~kelson