<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Hello Richard:<br></span></div><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Richard Tew <richard.m.tew@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Andrew Francis <andrewfr_ice@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> Armin Rigo <arigo@tunes.org>; "pypy-dev@python.org" <pypy-dev@python.org><br><b><span style="font-weight: bold;">Sent:</span></b> Monday, September 26, 2011 7:50 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [pypy-dev] Stacklets<br></font><br>On Tue, Sep 27, 2011 at 1:21 AM, Andrew Francis <<a
ymailto="mailto:andrewfr_ice@yahoo.com" href="mailto:andrewfr_ice@yahoo.com">andrewfr_ice@yahoo.com</a>> wrote:<br>AF> Welll the easiest thing to do is to see if import _continuation fails. And<br>AF> if it does fail, try to import greenlets. Also keep the old greenlet code. This is very much the way <br>AF>the previous stackless.py worked.<br><br>>Wouldn't that complicate the code unnecessarily?<br><br>It complicates the code a bit more. However Stackless Python's big problem is that people do <br>not want to install another Python interpreter. Stackless.py with greenlets gives folks one less excuse<br>not to test drive Stackless.<br><br>> Perhaps a better way would be to put the burden on the greenlet users and if they wish to<br>>share the implementation, they should write an emulation layer for continuations.<br><br>How can this be better? My own experiences: I greatly benefited from not having to worry about greenlets and
being allowed to focus solely on select(). If users have to write their own emulation layer, I see major two things happening: 1) folks walk away. 2) One gets a proliferation of emulation layers - wasted manpower. As it stands the PyPy developers made the right choice.<br><br>As an example, look at the number of spinoffs from Stackless and stackless.py due to a lack of <br>networking.<br><br>AF> The other branch would be experimental. Wilder stuff would be done there.<br><br>>Sounds like a good idea to me. As long as any new or altered features<br>>do not make it into what is labelled as an implementation of the<br>>Stackless API without also being accepted into Stackless itself.<br><br>Richard, in the long run, people will use whatever solves their problems and creates opportunities. I don't know about you but I'm interested in using PyPy and stackless.py to prototype new concurrency constructs that I want to use.... and in the
process, throwing the prototypes out there to see what sticks. <br><br>Cheers,<br>Andrew<br><br><br><br><br></div></div></div></body></html>