[Stackless] unexpected tasklet & channel behaviour

Richard Tew richard.m.tew at gmail.com
Wed Nov 1 11:09:22 CET 2006

On 11/1/06, Christian Tismer <tismer at stackless.com> wrote:
> Well, I never found a clean way to run exactly one tasklet,
> and I think it is not really possible. Collaborative
> solutions like yours can of course work. But I cannot
> imagine how we should get complete control over a tasklet
> in a general way.
> I agree that tasklet.run is promising something that does not
> exist.
> Stackless was not designed to run a specific tasklet, it was
> more like letting things happen using the round-robin
> approach. Maybe a coroutine interface would be more appropriate
> to specify what a run() should do?

Don't worry about it.  I think you are spot on with what you say
above.  People just have to understand that the scheduler is
the core of Stackless, and that it is impractical to promise things
like running of a single tasklet, given that you do not know what
might happen in that tasklet.


Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list