<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>To paraphrase a known individual: if it sounds good it is good. </div>
<div><br>
</div>
<div><br>
</div>
Sent from the ćther.<br>
<br>
-------- Original message --------<br>
From: Richard Tew <br>
Date:07/02/2014 18:52 (GMT+00:00) <br>
To: The Stackless Python Mailing List <br>
Subject: Re: [Stackless] liberating stackless.run() <br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Sounds good.<br>
<br>
On 2/8/14, Kristján Valur Jónsson <kristjan@ccpgames.com> wrote:<br>
> So,<br>
> I have a very nice change in the wings for stackless.<br>
> in my stackless-scratch repo<br>
> (<a href="https://bitbucket.org/krisvale/stackless-scratch">https://bitbucket.org/krisvale/stackless-scratch</a>) there is a branch called<br>
> nested-run.<br>
><br>
> This allows stackless.run() to be called from any tasklet. What is more,<br>
> more than one stackless.run() can be in effect. They nest and the innermost<br>
> is in effect at any one time.<br>
> This is useful because we can now write code that runs e.g. the event loop<br>
> on a tasklet. This simplifies e.g. monkeypatching code.<br>
><br>
> There is a bunch of unittests involved, testing this.<br>
><br>
> In the process, I discovered that the deadlock detection and handling code<br>
> in 2.7 was broken in various ways. I have fixed that and added unittests in<br>
> stackless-dev/stackless.<br>
><br>
> Cheers,<br>
><br>
> K<br>
><br>
><br>
<br>
_______________________________________________<br>
Stackless mailing list<br>
Stackless@stackless.com<br>
<a href="http://www.stackless.com/mailman/listinfo/stackless">http://www.stackless.com/mailman/listinfo/stackless</a><br>
<br>
</div>
</span></font>
</body>
</html>