That's a great way of thinking about async structure - and perhaps
surprisingly (since switching from asyncio or trying fledgling
implementations as part of my day job is a no-go ;) immediately useful. A
large part of what I do is wrap existing libraries so they can be used with
asyncio- the idea b
Maybe this one https://github.com/malinoff/aionursery ?
On 26/02/19 02:14, Nathaniel Smith wrote:
On Mon, Feb 25, 2019 at 4:15 PM Josh Quigley <0zer...@gmail.com> wrote:
I've realised the error of my ways: because Task separates the scheduling from
the response handling, you cannot know if an
On Mon, Feb 25, 2019 at 4:15 PM Josh Quigley <0zer...@gmail.com> wrote:
>
> I've realised the error of my ways: because Task separates the scheduling
> from the response handling, you cannot know if an exception is unhandled
> until the task is deleted. So in my example the reference means the ta
I've realised the error of my ways: because Task separates the scheduling
from the response handling, you cannot know if an exception is unhandled
until the task is deleted. So in my example the reference means the task is
not deleted, so the exception is not yet unhandled.
This is in contrast to
