Adding nurseries to asyncio (or wherever in the stdlib they fit -- if they
can be independent from asyncio and shared between asyncio and trio, all
the better).
On Thu, Apr 26, 2018 at 10:03 PM, Nathaniel Smith wrote:
> On Wed, Apr 25, 2018 at 9:43 PM, Guido van Rossum
On Wed, Apr 25, 2018 at 3:17 AM, Antoine Pitrou wrote:
> On Wed, 25 Apr 2018 02:24:15 -0700
> Nathaniel Smith wrote:
>> Hi all,
>>
>> I just posted another essay on concurrent API design:
>>
>>
On Wed, Apr 25, 2018 at 9:43 PM, Guido van Rossum wrote:
> Now there's a PEP I'd like to see.
Which part?
-n
--
Nathaniel J. Smith -- https://vorpus.org
___
Async-sig mailing list
Async-sig@python.org
On Thu, Apr 26, 2018 at 7:55 PM, Dima Tisnek wrote:
> My 2c after careful reading:
>
> restarting tasks automatically (custom nursery example) is quite questionable:
> * it's unexpected
> * it's not generally safe (argument reuse, side effects)
> * user's coroutine can be
My 2c after careful reading:
restarting tasks automatically (custom nursery example) is quite questionable:
* it's unexpected
* it's not generally safe (argument reuse, side effects)
* user's coroutine can be decorated to achieve same effect
I'd say just remove this, it's not relevant to your
Now there's a PEP I'd like to see.
On Wed, Apr 25, 2018 at 2:24 AM, Nathaniel Smith wrote:
> Hi all,
>
> I just posted another essay on concurrent API design:
>
> https://vorpus.org/blog/notes-on-structured-concurrency-or-
> go-statement-considered-harmful/
>
> This is the one
On Wed, 25 Apr 2018 02:24:15 -0700
Nathaniel Smith wrote:
> Hi all,
>
> I just posted another essay on concurrent API design:
>
> https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
>
> This is the one that finally gets at the core