I think despite flow control and buffer bloat issues, because it's a more mature library (interaction with other services is easier because asyncio versions of those client libraries already exist), I should re-add asyncio support, but this time using the streams API.
It shouldn't be hard to support asyncio and trio at the same time, and inject the desired implementation into server/client instances.