Telethon

I don't have a book recommendation ready, but if you want to see how async can be used in a large codebase, have a look at the telethon [1] library. It's a python library for telegram and one of the few that actually implement MTProto. It's huge, generates a large chunk of its machinery automatically from the MTProto specs and is extremely (!) well structured. This is much more useful than the typical "let's write a single-run example with async" blog post. [1] https://github.com/LonamiWebs/Telethon

The telethon library [1] is a very interesting case. It's fully async, implements the weird binary mtproto protocol, has optional C components for speedup and is partly auto-generated from protocol specs. It is an incredibly complex piece of code, but is immensely rigidly structured, typed and makes heavy use of OO to remain readable and manageable. So instead of perfect hypothetical textbook code, I think this is a very instructive realistic project. [1] https://github.com/LonamiWebs/Telethon

Trio has a really nice aesthetic, although I personally found the concept of nurseries a bit weird at first. However, I'd be interested to hear why one would use trio today instead of the more widely used (and official) built-in python async / asyncio stack? Are there any major libraries using trio? (To see how a large, rather well-structured async codebase looks like, see Telethon, an async and complete MTProto implementation [1]) [1] https://github.com/LonamiWebs/Telethon

> As far as I can tell, the only implementations for the platforms I care about are the “official” ones Telethon (https://github.com/LonamiWebs/Telethon) is a decent up to date (with MTProto) independent clean-room client implementation in the form of a Python lib. You might consider trying to take care about it.