Yury Selivanov - async/await in Python 3.5 and why it is awesome

[@aleksandrkurlov3219]

One of the best talk for getting started with asyncio

[@pynchia4119]

Good talk. And yes, asyncio documentation is still pretty awful in 2018

[@АртемШестаков-д9в]

...still pretty awful in 2020

[@Darqonik]

…still pretty awful in 2023

[@mihailtemelkov32]

asyncio was added in 3.4, not 3.3 (the slide that starts at 3:00)

[@ubergarm]

Great talk! Good signal to noise ratio! Love the jokes! This guy understands my pain! 1) kzbin.info/www/bejne/o2Obl5yEbt6SqJo "5 Obvious ways to do coroutines..." 2)kzbin.info/www/bejne/o2Obl5yEbt6SqJo -"asyncio is simple..." Thanks for developing the uvloop implementation because: github.com/channelcat/sanic/ Now I can reach for python instead of golang or node for backend apps again! Cheers!

[@naeemkhoshnevis]

Good talk.

[@mckenziejohan4149]

very good talks but too short... 😭😭😭😭 Other high-level asyncio APIs, not covered here, include: stream, a set of high-level networking primitives for managing asynchronous TCP events. lock, event, condition, async analogs of the synchronization primitives provided in the threading module. subprocess, a set of tools for running async subprocesses, such as shell commands. queue, an asynchronous analog of the queue module. exception, for handling exceptions in async code.

[@DenisG631]

SelivAnov, not SelivanOv ;)

[@De4sher]

"The asyncio documentation is simple. It only takes you 5 days to read it and a couple of months to digest it....and then you can use it" kzbin.info/www/bejne/o2Obl5yEbt6SqJom26s :D Async is not simple. It is hard to understand. It's totally worth it, and it's very awesome, but still, let's not kid ourselves. For me, async workflows were harder to understand than threaded ones.