Is Stackless Python DEAD?

[Guido Stepken]

A.M. Kuchling wrote:

> On Mon, 05 Nov 2001 02:13:00 GMT,
> Frederic Giacometti <frederic.giacometti at arakne.com> wrote:
>>This words seems to point out that the actual reason is not technical...
>>This is definitely not a word from the realm of engineering, but more from
>>someone sense of his core self being disturbed by an outsider.
> 
> Not at all.  Stackless would have ramifications not just for a few
> files in the core, but also for all the extension modules that come
> with Python and for all the authors of third-party extension modules.
> In terms of number of files affected, "intrusive" isn't a bad word to
> describe the Stackless patches.
> 
> --amk
> 
IMHO, a lot of more work should be invested in stackless python, perhaps 
for a dr. theses or diploma work ....

Why ? Python is even running on palm Vx and iPaq. Doing multitasking with 
threads isn't that complicated, but very much easier to write code with 
continuations, if one has understood once the big advantage....
Python is becoming a common programming language for everybody, because it 
i s really easy to learn ....i have learned basic, 6502 assembler, pascal, 
delphi, c, c++, prolog, lisp, PHP, PERL  and now Python.
Compared to JAVA, Python is really RAD (RApid Development), about 3 times 
faster.....and you can compile java bytecode .... 
JPYTHON is a problem - continuations have to be translated internally into 
green threads - a masterpiece for this person, who will succeedd.....

guys (Guido v. Rossum, PHIL (PYQT) and all others ..), keep up the good 
work ....!

regards, Guido Stepken