Re: [pypy-dev] Win32 build of the release 1.7

2011-12-01 Thread Armin Rigo
Hi, On Thu, Dec 1, 2011 at 18:38, Carlos Eduardo wrote: > (...) Probably this is due to JIT being disabled when using Stackless > features. > > Other than the performance, it's working fine with the examples I tested from: > http://code.google.com/p/stacklessexamples/ Great to know. Indeed, it

Re: [pypy-dev] Win32 build of the release 1.7

2011-12-01 Thread Carlos Eduardo
Armin Rigo tunes.org> writes: > > Hi, > > The build has been "officialized" and is now available from > https://bitbucket.org/pypy/pypy/downloads . > > A bientôt, > > Armin. > I tested the 1.7 release on Windows XP using some Stackless Python examples I have. Most of them worked fine, the

Re: [pypy-dev] Win32 build of the release 1.7

2011-11-29 Thread Armin Rigo
Hi, The build has been "officialized" and is now available from https://bitbucket.org/pypy/pypy/downloads . A bientôt, Armin. ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev

Re: [pypy-dev] Win32 build of the release 1.7

2011-11-29 Thread Maciej Fijalkowski
On Tue, Nov 29, 2011 at 3:58 PM, Chris Wj 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 wrote: >> >> >> >> On Mon, Nov 28, 2011 at 9:40 PM, Alex Gaynor >> wrote: >>> >>> >>> This

Re: [pypy-dev] Win32 build of the release 1.7

2011-11-29 Thread Chris Wj
Similar experience with **2 for me on linux x64. On Mon, Nov 28, 2011 at 3:37 PM, mike c wrote: > > > On Mon, Nov 28, 2011 at 9:40 PM, Alex Gaynor wrote: > >> >> This appears to be totally broken independently of windows, on Linux I'm >> getting something that looks like sys.maxint instead of 0.

Re: [pypy-dev] Win32 build of the release 1.7

2011-11-28 Thread mike c
On Mon, Nov 28, 2011 at 9:40 PM, Alex Gaynor 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 i

Re: [pypy-dev] Win32 build of the release 1.7

2011-11-28 Thread Alex Gaynor
On Mon, Nov 28, 2011 at 6:36 AM, 刘振海 <1989l...@gmail.com> wrote: > Hi, > > Thanks for you guys to create such amazing interpreter. > > I try the numpypy module and find this. > > import numpypy as np > a=np.array([1,2,3]) > a**2 # here the result is [0, 0 ,0], I think this is a bug > a*2 # here th

Re: [pypy-dev] Win32 build of the release 1.7

2011-11-28 Thread 刘振海
Hi, Thanks for you guys to create such amazing interpreter. I try the numpypy module and find this. import numpypy as np a=np.array([1,2,3]) a**2 # here the result is [0, 0 ,0], I think this is a bug a*2 # here the result is [2,4,6] Regards, Liu Zhenhai 2011/11/28 Armin Rigo > Hi all, > >

[pypy-dev] Win32 build of the release 1.7

2011-11-27 Thread Armin Rigo
Hi all, We have a tentative Win32 build of PyPy 1.7 including both the JIT and Stackless features (the '_continuation' primitive module and the app-level 'stackless' and 'greenlet' modules). It built and passed a good proportion of tests. If you are interested in helping, could a few people try