Aymeric Augustin

> Funnily enough, you're making my point for me. This sounds like you're talking down to me. Please, let's have a constructive conversation or leave it there. I'm clear on...

No worries. Feels like we fell into a typical trap of open-source collaboration :-( If you have a WIP version of your anyio implementation somewhere, I'm genuinely interested in reading...

That's a fair point. I didn't have it in mind because I haven't come across "intermediate libraries" having this use case until now. Do you have examples? I'd like to...

BTW I have a working client now, with some truly outstanding code inside, but it works — like I said I'm learning about structured concurrency ;-) ```python # async with...

One one hand, this is clearly voiding the warranty :-) On the other hand, I don't see a better way to provide the API that I want to provide (`async...

It can work if the user takes responsibility: ```python async with trio.open_nursery() as nursery: connection = await connect(..., nursery=nursery) ``` Currently I'm +0 on including that in the API but...

> using a context-manager-per-connection which has an internal nursery would be the usual pattern for that. Yes, that's the recommend way to connect. The code snippet that I shared above...

Client is now feature-complete with 100% test coverage, although there's a bit of proof-reading and cleanup left. Moving on to server.

I am debating whether the method to close i/ connections and ii/ servers should be called `close` or `aclose`. The choice should be made according to the Principle of Least...

Green build. Woohoo. Still a few fixes + full proof-reading necessary.