Re: [Pytables-users] Slicing with index arrays

[travlr <vel...@gm...>]

The patch worked fine Francesc, and I'm going to work on the other parts as=
=20
you suggested. I'll get back to you soon.

Pete

On 7/18/05, Francesc Altet <fa...@ca...> wrote:
>=20
> A Monday 18 July 2005 16:39, travlr va escriure:
> > > However, your suggestion is quite good, and implementing it is a=20
> matter
> > > of adding a new case in the Column.__getitem__() special method.
> > > Something like:
> > >
> > > [...]
> > > elif isinstance(key, numarray):
> > > return self.table.readCoordinates(key, self.name <http://self.name> <
> http://self.name>)
> >
> > This is terrific. I'd also like to mention two things... setting the=20
> attr
> > vals via file.root.group.table.cols.blah[idx] =3D array ...would also b=
e
> > great. I believe this syntax congruency (a la numarray) should also be
> > extended to (py)tables.tables and (py)tables.array objects.
>=20
> Good suggestion. We will see what can we do. Nevertheless, it would be
> great if you can contribute the code (and docs) yourself.
>=20
> > I got an Error tossing in your patch :
> >
> > [...]
> > elif isinstance(key, numarray.numarraycore.NumArray):
> > return self.table.readCoordinates(key, self.name <http://self.name> <
> http://self.name>)
> > [...]
>=20
> Yes. This is a bug in readCoordinates. Try applying the attached patch
> as well.
>=20
> Cheers,
>=20
> --
> >0,0< Francesc Altet http://www.carabos.com/
> V V C=E1rabos Coop. V. Enjoy Data
> "-"
>=20
>=20
>=20
>