[Numpy-discussion] 64-bit Fedora 9 a=numpy.zeros(0x80000000, dtype='b1')
Nadav Horesh
nadavh@visionsense....
Sun Sep 13 05:39:23 CDT 2009
Could it be a problem of python version? I get no error with python2.6.2 (on amd64 gentoo)
Nadav
-----הודעה מקורית-----
מאת: numpy-discussion-bounces@scipy.org בשם David Cournapeau
נשלח: א 13-ספטמבר-09 09:48
אל: Discussion of Numerical Python
נושא: Re: [Numpy-discussion] 64-bit Fedora 9 a=numpy.zeros(0x80000000, dtype='b1')
Charles R Harris wrote:
>
>
> On Sat, Sep 12, 2009 at 9:03 AM, Citi, Luca <lciti@essex.ac.uk
> <mailto:lciti@essex.ac.uk>> wrote:
>
> I just realized that Sebastian posted its 'uname -a' and he has a
> 64bit machine.
> In this case it should work as mine (the 64bit one) does.
> Maybe during the compilation some flags prevented a full 64bit
> code to be compiled?
> __
>
>
> Ints are still 32 bits on 64 bit machines, but the real question is
> how python interprets the hex value.
That's not a python problem: the conversion of the object to a C
int/long happens in numpy (in PyArray_IntpFromSequence in this case). I
am not sure I understand exactly what the code is doing, though. I don't
understand the rationale for #ifdef/#endif in the one item in shape
tuple case (line 521 and below), as well as the call to PyNumber_Int,
cheers,
David
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 3965 bytes
Desc: not available
Url : http://mail.scipy.org/pipermail/numpy-discussion/attachments/20090913/f10474f5/attachment.bin
More information about the NumPy-Discussion
mailing list