Talk:Stackless Python
From Wikipedia, the free encyclopedia
[edit] No more continuations?
I wish to mention that this artical is several years out of date. Stackless no longer supports continuations, as mentioned in a message posted by Christian Tismer to the Stackless Mailing list on March, 2004. Newer versions have light weight threads called tasklets. --Lenard Lindstrom 17:42, 24 July 2005 (UTC)
partially true
Well this is true in the sense that the article includes old information. Continuations were the target of the first implementations, later on I changed to the less powerful but easier to understand taskletmodel, which is some kind of one-shot continuations. Actually, this appears to be the only kind of continuations commonly understood.
partially false
It is false in the sense that Stackless of course has continuations in their full sense, that is you can take a snapshot of a running program and start this several times, concurrently. It is not directly supported any longer, but running tasklets may be pickled. It is upt o the user to load a stored tasklet from disk multiple times. This is almost like full continuations, despite the fact that the variables are not shared between the instances.
Christian Tismer, creator of Stackless Python -- 15:02, 18 August 2005
- Isn't it crucial for invoked continuations to refer to the same environment as they did when they were captured? I think most of the things continuations are used for are impossible if that isn't the case.
- And about the tasklets: are they really one-shot continuations, or coroutines? In other words, can you invoke previously-captured continuations of a tasklet, or just suspend/resume the current tasklet? --Piet Delport 10:10, 8 March 2006 (UTC)
[edit] Expanding on this page
I think that talking to the author of the following article and reusing the bulk of it where it doesn't specifically apply to game programming would allow a more extensive entry here: http://harkal.sylphis3d.com/2005/08/10/multithreaded-game-scripting-with-stackless-python/
Richard Tew, user of Stackless Python
