<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> Carl Friedrich Bolz <cfbolz@gmx.de>; "pypy-dev@python.org" <pypy-dev@python.org><br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, September 27, 2011 7:57 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [pypy-dev] Stacklets<br><br></font>>Can't you do that in another file that
doesn't represent itself as an<br>>implementation of Stackless with no loss to your freedoms? <br><br>Yes Richard, I can give a file another name. If I called the experimental module something-that-I-read-in-a-paper-and-decided-to-implement-in-StacklessPy-because-I-do-not-like-hacking-in-C.py,<br>would that satisfy you? Regardless of name, this other file sitting in an experimental branch claiming <br>to be a representation of stackless.py would implement the entire Stackless API and about 60% of the current stackless.py's code base.<br><br>More importantly, quirks and bugs in the overlapping 60% of the code base, I would be inclined to fix in the legitimate stackless.py as well. <br><br>"What's in a name? that which we call a rose by any other name would smell as sweet"<br><br>>This way, anyone who would use stackless.py would get the stable set of features<br>>and API that Stackless has had for over five years now and likely the
ability to switch between<br>> the two implementations.<br><br>And what is stopping folks from using a stackless.py that moves lockstep with Stackless Python, while there is a stackless_v3.py lay in an experimental branch? Isn't this sort of like Python 2.x existing while Python 3.x was being worked on and put as alphas? <br><br>>Or am I misunderstanding?<br><br>Yes Richard you are misunderstanding. What I am working on (or have in mind) is not Concurrence, or a gEvent like package but potential new Stackless Python features. And you know this. To me the real issue is NIH invented here. <br><br>One of the things that will complicate Stackless Python's world is that advances courtesy of PyPy make experimenting with Stackless Python and bypassing C based Stackless Python increasingly the most attractive evolutionary path. Rather than quibbling, figure out how to take best advantage of
this.<br><br>Cheers,<br>Andrew<br></div></div></div></body></html>