Re: [Numpy-discussion] bug with numpy 2 ** N

2011-03-23 Thread Matthieu Brucher 
Hi,

I don't thnk this is a bug. You are playign with C integers, not Python
integers, and the former are limited. It's a common "feature" in all
processors (even DSPs).

Matthieu

2011/3/23 Dmitrey 

>  >>> 2**64
> 18446744073709551616L
> >>> 2**array(64)
> -9223372036854775808
> >>> 2**100
> 1267650600228229401496703205376L
> >>> 2**array(100)
> -9223372036854775808
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>


-- 
Information System Engineer, Ph.D.
Blog: http://matt.eifelle.com
LinkedIn: http://www.linkedin.com/in/matthieubrucher
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] bug with numpy 2 ** N

2011-03-23 Thread Dmitrey 
 >>> 2**64
   18446744073709551616L
   >>> 2**array(64)
   -9223372036854775808
   >>> 2**100
   1267650600228229401496703205376L
   >>> 2**array(100)
   -9223372036854775808
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion