On Tue, 20 Jun 2006 21:05:51 +0200
Thomas Heller <[EMAIL PROTECTED]> wrote:
> Travis Oliphant schrieb:
> > I just updated the array interface page to emphasize we now have version
> > 3. NumPy still supports objects that expose (the C-side) of version 2
> > of the array interface, though.
> >
Thomas Heller wrote:
> Travis Oliphant schrieb:
>> I just updated the array interface page to emphasize we now have
>> version 3. NumPy still
>
> If current implementations of the array interface use this pointer for
> other things (like keeping a reference to the array object), that's
> fine,
Travis Oliphant schrieb:
> I just updated the array interface page to emphasize we now have version
> 3. NumPy still supports objects that expose (the C-side) of version 2
> of the array interface, though.
>
> The new interface is basically the same except (mostly) for asthetics:
> The diff
Hello all
On Fri, 16 Jun 2006, Travis Oliphant wrote:
> I just updated the array interface page to emphasize we now have version
> 3. NumPy still supports objects that expose (the C-side) of version 2
> of the array interface, though.
> Please voice concerns now if you have any.
In the d
I noticed in your note labeled 'June 16, 2006' that you refer to the
"desc" field. However, in the struct description above, there is only a
field named "descr".
Also, I suggest that you update the information in the comments of descr
field of the structure description to contain the fact that
On 6/16/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> There is talk of ctypes supporting the new interface which is a worthy
> development. Please encourage that if you can.
That would certainly be excellent, esp. given how ctypes is slated to
be officially part of python 2.5. I think it wou
