[Stackless] liberating stackless.run()

Kristján Valur Jónsson kristjan at ccpgames.com
Fri Feb 7 21:37:29 CET 2014

To paraphrase a known individual: if it sounds good it is good.

Sent from the æther.

-------- Original message --------
From: Richard Tew
Date:07/02/2014 18:52 (GMT+00:00)
To: The Stackless Python Mailing List
Subject: Re: [Stackless] liberating stackless.run()

Sounds good.

On 2/8/14, Kristján Valur Jónsson <kristjan at ccpgames.com> wrote:
> So,
> I have a very nice change in the wings for stackless.
> in my stackless-scratch repo
> (https://bitbucket.org/krisvale/stackless-scratch) there is a branch called
> nested-run.
> This allows stackless.run() to be called from any tasklet.  What is more,
> more than one stackless.run() can be in effect.  They nest and the innermost
> is in effect at  any one time.
> This is useful because we can now write code that runs e.g. the event loop
> on a tasklet.  This simplifies e.g. monkeypatching code.
> There is a bunch of unittests involved, testing this.
> In the process, I discovered that the deadlock detection and handling code
> in 2.7 was broken in various ways.  I have fixed that and added unittests in
> stackless-dev/stackless.
> Cheers,
> K

Stackless mailing list
Stackless at stackless.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20140207/b6c32fe4/attachment.html>

More information about the Stackless mailing list