Curt Hagenlocher skrev:
Does that not happen on non-Windows platforms? 2**31 can't be
represented as a 32-bit signed integer, so it's automatically promoted
to a long.
Yes you are right.
I've now traced down the problem to an integer overflow in NumPy.
It seems to have this Pyrex code:
cd
On Sun, Nov 1, 2009 at 8:22 PM, Sturla Molden wrote:
>
> Why does this happen?
>
> >>> type(2**31-1)
>
Does that not happen on non-Windows platforms? 2**31 can't be
represented as a 32-bit signed integer, so it's automatically promoted
to a long.
--
Curt Hagenlocher
c...@hagenlocher.org
___
Why does this happen?
>>> type(2**31-1)
It seems to have broken NumPy's RNG on Win32.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pyth
