30K views · May 13, 2018 · 32:17 · 2 HN recommenders · 3 mentions · discussed 2020–2023
Nathaniel J. Smith's PyCon 2018 talk introducing Trio, a Python concurrency library designed around usability and structured concurrency. He live-codes a problem and analyzes pitfalls in other async libraries.
Why Hacker News points people here: Recommended as a clear introduction to structured concurrency and as an explanation of subtle asyncio bugs that Trio avoids.
“one of the best explanations I've seen about what subtle bugs are easy to make with asyncio”HN comment, 2021
“one of the best explanations I've seen about what subtle bugs are easy to make with asyncio”
Explains subtle asyncio bugs and how trio addresses them
The video (or blog post) below is one of the best explanations I've seen about what subtle bugs are easy to make with asyncio, why it's easy to make them, and how the trio library addresses them. But yes, consider alternatives before you pick asyncio as your approach! Talk: this video Blog post: link
“A useful introduction to the ideas is in Nathaniel's PyCon 2018 talk on trio”
Useful introduction with live-coded concurrency problem
A useful introduction to the ideas is in Nathaniel's PyCon 2018 talk on trio [1], where he live-codes a solution to a concurrency-spaghetti problem. [1] this video
“I think it's usually called Happy Eyeballs”
Happy Eyeballs concept for multiple requests
Great list. That last suggestion (Multiple requests) can be tough to implement correctly, I think it's usually called Happy Eyeballs: this video
