[pypy-dev] PyPy3 2.1 beta 1 released

PyPy3 2.1 beta 1 We're pleased to announce the first beta of the upcoming 2.1 release of PyPy3. This is the first release of PyPy which targets Python 3 (3.2.3) compatibility. We would like to thank all of the people who donated_ to the `py3k proposal`_ for suppo

Re: [pypy-dev] memory leak in pypy

Ok, I tracked it down. For some reason pydev (eclipse) was randomly choosing between pypy and python2.7 on each run (I discovered this when watching what was happening in top). This explains why it was so flakey. Sorry for the confusion. I have no idea how I'm going to debug this further. (OT:

Re: [pypy-dev] Threading in RPython

On Tue, Jul 30, 2013 at 3:38 AM, Armin Rigo wrote: > Hi Sean, > > On Sun, Jul 7, 2013 at 10:23 PM, Sean Fisk wrote: > > Sorry, I didn't make it clear: my project is actually an interpreter for > a > > stencil-based language that is used for solving partial differential > > equations. So I think

Re: [pypy-dev] memory leak in pypy

Hi Vasily, On Tue, Jul 30, 2013 at 2:02 PM, Vasily Evseenko wrote: > It seems to be range / xrange issue. > range allocates all data in a moment when xrange acts like an iterator. Not in PyPy. Armin ___ pypy-dev mailing list pypy-dev@python.org http:

Re: [pypy-dev] memory leak in pypy

Hi, It seems to be range / xrange issue. range allocates all data in a moment when xrange acts like an iterator. On 07/30/2013 01:01 PM, Maciej Fijalkowski wrote: > This sounds odd. My PyPy does not leak memory in this example. Can you > please double check? > > On Tue, Jul 30, 2013 at 2:43 AM, Na

Re: [pypy-dev] Threading in RPython

Hi Sean, On Sun, Jul 7, 2013 at 10:23 PM, Sean Fisk wrote: > Sorry, I didn't make it clear: my project is actually an interpreter for a > stencil-based language that is used for solving partial differential > equations. So I think that RPython is the right tool to an extent. It worked > very well

Re: [pypy-dev] memory leak in pypy

This sounds odd. My PyPy does not leak memory in this example. Can you please double check? On Tue, Jul 30, 2013 at 2:43 AM, Nathan Hurst wrote: > I was playing with this simple function to compute uint/3. It does > not (afaict) directly allocate any memory, but when run it rapidly > consumes al

[pypy-dev] Fwd: Build failed in Jenkins: pypy #887

the nightly build crashes strangely -- Forwarded message -- From: "Jenkins" Date: Tue, Jul 30, 2013 at 2:48 AM Subject: Build failed in Jenkins: pypy #887 To: fij...@gmail.com See -- [...truncated 3127 lines