Robert Kern wrote:
Francesc Altet wrote:
A Divendres 09 Juny 2006 11:54, Albert Strasheim va escriure:
Just out of curiosity:
In [1]: x = N.array([])
In [2]: x.__array_data__
Out[2]: ('0x01C23EE0', False)
Is there a reason why the __array_data__ tuple stores the address as a hex
string? I
A Divendres 16 Juny 2006 21:25, Thomas Heller va escriure:
Robert Kern wrote:
Like how Win64 uses 32-bit longs and 64-bit pointers. And then there's
signedness. Please don't use Python ints to encode pointers. Holding
arbitrary pointers is the job of CObjects.
(Sorry, I'm late in reading
Thomas Heller wrote:
Robert Kern wrote:
Francesc Altet wrote:
A Divendres 09 Juny 2006 11:54, Albert Strasheim va escriure:
Just out of curiosity:
In [1]: x = N.array([])
In [2]: x.__array_data__
Out[2]: ('0x01C23EE0', False)
Is there a reason why the __array_data__
Albert Strasheim wrote:
Hello all
-Original Message-
From: [EMAIL PROTECTED] [mailto:numpy-
[EMAIL PROTECTED] On Behalf Of Travis Oliphant
Sent: 08 June 2006 22:27
To: numpy-discussion
Subject: [Numpy-discussion] Array Protocol change for Python 2.6
...
I would like to eliminate
Tim Hochberg wrote:
Sasha wrote:
On 6/8/06, David M. Cooke [EMAIL PROTECTED] wrote:
...
+0 for name change; I'm happy with it as an attribute.
My rule of thumb for choosing between an attribute and a method is
that attribute access should not create new objects.
Interesting
On 6/9/06, Travis Oliphant [EMAIL PROTECTED] wrote:
... In NumPy this is not quite the rule followed.
Bascially attributes are used when getting or setting intrinsinc
properties of the array. Attributes are used for properties that are
important in defining what an array *is*. The flags
On Fri, 09 Jun 2006 16:03:32 -0700
Andrew Straw [EMAIL PROTECTED] wrote:
Tim Hochberg wrote:
Which of the following should we require for an object to be supporting
the array interface? Here a producer is something that supplies
array_struct or array_interface (where the latter is the
