[Numpy-discussion] Array Protocol change for Python 2.6

Robert Kern robert.kern at gmail.com
Fri Jun 9 12:30:20 EDT 2006

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 would guess that this representation of the address isn't the
>>most useful one for most applications.
> Good point. I hit this before and forgot to send a message about this. I agree 
> that a integer would be better. Although, now that I think about this, I 
> suppose that the issue should be the difference of representation of longs in 
> 32-bit and 64-bit platforms, isn't it?

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.

Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
  -- Umberto Eco

More information about the NumPy-Discussion mailing list