Re: [pypy-dev] Stacklets

2011-09-28 Thread Andrew Francis
Hello Richard: From: Richard Tew To: Andrew Francis Cc: Carl Friedrich Bolz ; "pypy-dev@python.org" Sent: Tuesday, September 27, 2011 7:57 PM Subject: Re: [pypy-dev] Stacklets >Can't you do that in another file that doesn't

Re: [pypy-dev] Stacklets

2011-09-27 Thread Richard Tew
On Wed, Sep 28, 2011 at 2:16 AM, Andrew Francis wrote: > At the risk of this sounding like a rant or being off-topic, it seems to me > the big picture that is getting lost is that stackless.py and PyPy makes it > easier for individuals to prototype new ideas for Stackless Pythons and > probably Py

Re: [pypy-dev] Stacklets

2011-09-27 Thread Andrew Francis
Hi Carl: From: Carl Friedrich Bolz To: pypy-dev@python.org Sent: Tuesday, September 27, 2011 11:15 AM Subject: Re: [pypy-dev] Stacklets >Throwing a prototype out is not the same as giving the prototype a >semi-official blessing by packaging it >wit

Re: [pypy-dev] Stacklets

2011-09-27 Thread Carl Friedrich Bolz
On 09/27/2011 05:03 PM, Andrew Francis wrote: >Sounds like a good idea to me. As long as any new or altered features >do not make it into what is labelled as an implementation of the >Stackless API without also being accepted into Stackless itself. Richard, in the long run, people will use wh

Re: [pypy-dev] Stacklets

2011-09-27 Thread Andrew Francis
Hello Richard: From: Richard Tew To: Andrew Francis Cc: Armin Rigo ; "pypy-dev@python.org" Sent: Monday, September 26, 2011 7:50 PM Subject: Re: [pypy-dev] Stacklets On Tue, Sep 27, 2011 at 1:21 AM, Andrew Francis wrote: AF> Welll the easiest t

Re: [pypy-dev] Stacklets

2011-09-26 Thread Richard Tew
On Tue, Sep 27, 2011 at 1:21 AM, Andrew Francis wrote: > Welll the easiest thing to do is to see if import _continuation fails. And > if it does fail, try to import > greenlets. Also keep the old greenlet code. This is very much the way the > previous stackless.py > worked. Wouldn't that complica

Re: [pypy-dev] Stacklets

2011-09-26 Thread Andrew Francis
Hi Armin: From: Armin Rigo To: Andrew Francis Cc: Александр Седов ; "pypy-dev@python.org" Sent: Monday, September 26, 2011 9:05 AM Subject: Re: [pypy-dev] Stacklets >Feel free to propose concrete improvements. Welll the easiest thing to do

Re: [pypy-dev] Stacklets

2011-09-26 Thread Armin Rigo
Hi, 2011/9/24 Andrew Francis : > A suggestion. Perhaps it would be good to keep the test for whether CPython is > the interpreter and greenlets ought to be used? Feel free to propose concrete improvements. As I said already, I implemented the code so far but I don't really have deep interest mys

Re: [pypy-dev] Stacklets

2011-09-24 Thread Andrew Francis
Hi Armin and Folks: From: Armin Rigo To: Александр Седов Cc: pypy-dev@python.org Sent: Friday, September 23, 2011 4:38 PM Subject: Re: [pypy-dev] Stacklets >Thanks!  Work in this direction is already well advanced.  More >precisely, the directory pypy/

Re: [pypy-dev] Stacklets

2011-09-23 Thread Armin Rigo
Hi, 2011/9/23 Александр Седов : > I'm interested in porting _stackless to stacklets (and also probably > making it inter-thread). Thanks! Work in this direction is already well advanced. More precisely, the directory pypy/module/_stackless is obsolete and gone, and the pure Python module lib_py

Re: [pypy-dev] Stacklets

2011-09-23 Thread Александр Седов
2011/9/1 Armin Rigo : > Hi, > > The "stacklet" branch has been merged now.  The "_continuation" module > is available on all PyPys with or without the JIT on x86 and x86-64 > since a few days, and it will of course be part of release 1.6.1. > There is an almost-complete wrapper "greenlet.py".  For

Re: [pypy-dev] Stacklets

2011-09-01 Thread Armin Rigo
Hi, The "stacklet" branch has been merged now. The "_continuation" module is available on all PyPys with or without the JIT on x86 and x86-64 since a few days, and it will of course be part of release 1.6.1. There is an almost-complete wrapper "greenlet.py". For documentation and current limitat

Re: [pypy-dev] Stacklets

2011-08-12 Thread Armin Rigo
Hi Anto, On Fri, Aug 12, 2011 at 2:22 PM, Antonio Cuni wrote: > Are the caller/callee genlets symmetrical? Yes; gen.next() is exactly like gen.send(None), just like with generators. Well it's maybe just rambling and the interface will change again next hour, but the idea is as follows. If you

Re: [pypy-dev] Stacklets

2011-08-12 Thread Antonio Cuni
Hi Armin, On 11/08/11 18:46, Armin Rigo wrote: Moreover, we can give it an interface very similar to generators. A genlet object has a primitive method send(x), a wrapper next() that just calls send(None), and is an iterator. Example: @genlet def f(gen, a, b): for i in range(a, b):

Re: [pypy-dev] Stacklets

2011-08-11 Thread Armin Rigo
Re-hi, On Thu, Aug 11, 2011 at 10:59 AM, Armin Rigo wrote: > Ah, I think it's what you get if you assume that your language has > callcc but no exceptions, and explicitly implement exceptions on top > of callcc. Ok, after a fruitful discussion on IRC (thanks Da_Blitz), here's yet another slightl

Re: [pypy-dev] Stacklets

2011-08-11 Thread Armin Rigo
Re-hi, On Thu, Aug 11, 2011 at 10:46 AM, Armin Rigo wrote: > I suppose this is already well-known, but I couldn't find an obvious > reference. Ah, I think it's what you get if you assume that your language has callcc but no exceptions, and explicitly implement exceptions on top of callcc. At e

[pypy-dev] Stacklets

2011-08-11 Thread Armin Rigo
Hi all, Some progress report from my side: I am working on "stacklets", which is, as the name implies, similar to Stackless. It is a rewrite of tealets, which was itself a greenlet-like replacement for Stackless Python. (Yes, "tealet" because of "greenlet": green tea... last time I can do the jo