On Tue, Nov 29, 2011 at 3:58 PM, Chris Wj <chris...@gmail.com> wrote: > Similar experience with **2 for me on linux x64.
This should be fixed by now. You can check tomorrow nightly > > On Mon, Nov 28, 2011 at 3:37 PM, mike c <coolbutusel...@gmail.com> wrote: >> >> >> >> On Mon, Nov 28, 2011 at 9:40 PM, Alex Gaynor <alex.gay...@gmail.com> >> wrote: >>> >>> >>> This appears to be totally broken independently of windows, on Linux I'm >>> getting something that looks like sys.maxint instead of 0. Can you file a >>> bug in our tracker for this? It's not going to be a release blocker for >>> windows, but it'll be fixed in the next release. >>> >> >> On OSX Snow Leopard pypy1.7 >> >> >>>> import numpypy as numpy >> >>>> a = numpy.array([1,2,3]) >> >>>> a**2 >> array([4607182418800017408, 4607182418800017408, 4607182418800017408], >> dtype=int64) >> >> mike >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev@python.org >> http://mail.python.org/mailman/listinfo/pypy-dev >> > > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
