Build Your Own Async

Yes, something like that. Like here's David's "Build Your Own Async" [1], which I prefer over Philip's (still extremely good) "What the heck is the event loop anyway?" [2]. It's one thing to tell how something works, but to successfully show what the hell its actually doing under the covers, just conveys much more information. [1] [VIDEO] [2] [LINK]

I've found this [1] screencast on the low-level principles of async in Python an amazing resource to understand async at a deep level. [1] [VIDEO]

I highly recommend Victor Skvortsov's exhaustive, 12-part series, "Python Behind the Scenes," a deep dive into the implementation details of just about every Python language feature one could possibly take for granted. There isn't a single one I haven't learned something from, but some of my personal favorites include: * Part 2, How the CPython compiler works: [LINK] * Part 6, How Python's object system works: [LINK] * Part 10, How Python dictionaries work: [LINK] * Part 13: The GIL and its effects on Python multithreading: [LINK] The whole series can be found here: [LINK] For a slightly higher-level (i.e., no macabre, low-level C code), but still incredibly enlightening dive into the "dark side" of Python, in particular various abuses and hexes for manipulating control flow, have a look at David Beazley's smorgasboard of keynote presentations like "Generators: The Final Frontier" ( [LINK] ), "Python Concurrency From The Ground Up" ( [LINK] ), and "Build Your Own Async" ( [VIDEO] ).

> I talk about generators as if they were the coroutine system in Python, but in fact, they’re one of two: Python also has a completely different kind of thing that it actually uses the name ‘coroutine’ for, in which function definitions start with async def and suspend with await . The async and await system of coroutines in Python is in fact layered on top of the yield system, via an intermediate construct called yield from —which isn’t even technically required, it’s just that implementing it as a loop passing values through from and to the subcoroutine is exceptionally tedious if done correctly[1] and can’t be abstracted as a function call. As a first approximation, await x in Python is equivalent to yield from x.__await__() . It should have been completely equivalent, arguably, but history got in the way. David Beazley has a talk[2] where he walks you through implementing an async runtime (to put it pompously) and you can see how the whole thing hangs together. It’s really quite simple, and in my experience it’s much better than trying to wrap your head around the asyncio docs, because while the language-level foundations are extremely nice and simple, asyncio the stdlib module just kind of sucks. [1] [LINK] [2] [VIDEO]