Fear and Awaiting in Async: A Savage Journey to the Heart of the Coroutine Dream

David Beazley
pyohio.org/sche...

[@ugood]

50:15 this realization is exactly the one that golang authors had back in 2007 when they envisioned exactly this very programming model of having normal, readable code that runs on coroutines, hiding behind a single keyword, but instead of "async" they chose "go". it's incredible how genius people end up on finding the same genius solutions to the same problem. Your book made me interested in programming with it's alive and practical approach but your python talks made me mature and I eventually switch to golang. Very thankful and grateful to you, Dear David 🙏❤

[@rohitbhanot7809]

I don't know but this guy has a knack of making astoundingly complex concepts seems buttery smooth and fairly understandable. I mean i have gone through half a dozen talks on async in last 2 days ans no one seems to explain it well enough to be grasped by a beginner. And this reminds me of a quote by Albert Einstein "If you can't something , you don't understand it well enough then"

[@mcspud]

Another amazing Beazley talk! Thanks!

[@BeatButton]

Note: as of Python 3.6, await and async for can be used in comprehensions and generator expressions

[@chris8443]

For those who see this and are curious, see PEP-530.

[@cenntraru]

Wow! I am deeply amazed! This time it's not only an as always interesting talk but also a game-changing async library presentation. Bravo, David!

[@KhaledKimboo4]

Async is like a plague, the moment it touches your code, it'll spread all over the place, and there's no going back

[@vme50eatkfc]

I saw your last talk, it's so amazing

[@hyperboogie]

Eye opening!!!

[@PixelPhobiac]

I love all your drug-references.

[@addychavs822]

cool talk 👌

[@y.5107]

incredible good

[@李梦龙-e4s]

Can anyone tell me what the code snippet tool David is using? Thx in advance.

[@SayandipDutta]

He has modded the python interpreter, in true dabeaz fashion.

[@shironbenyamini2798]

One thing that is unclear to me which came up a few times in the slides is for example: data = await client.recv(1000000) where "client" is a client socket. The problem is that as far as I know, client.recv is a normal function and not awaitable. Am I missing something?

[@davidtan8984]

quiet quiet quiet LOUD quiet quiet LOUD quiet quiet quiet LOUD quiet... jfc...

[@marqetintl]

I tested the awaitable decorator and it seems to not be working.. Saying "decorate() missing 1 required positional argument: 'asyncfn'"

[@liesdamnlies3372]

The copyright crap at the beginning is ridiculous. The art was original work. Derivative but still. That puts it under fair use. And then it's used as supporting material in a _programming_ talk? Any DMCA notice would be bogus.

[@JohnThorntonii]

The takedown story was a joke. His kids were the ones that did not want it shown on KZbin.

[@pengkim6062]

could you please tell me how did you do that when you type the keyword then came after the code sample accroding to in terminal, ex,: you type thread, then thread code sample show up.

[@MrMoon-hy6pn]

Years late but I could do it by creating a class that takes a python file, in a __repr__ method it takes that file does a bit for formatting to get the border and returns it as a string. I noticed he used the functions that are in the snippets so also in __repr__ it imports that module into the parent modules globals, e.g: class CodeSlide: def __init__(self, file: str): self.file = file def file_as_str(self): ... get file contents and format it ... return formatted def __repr__(self): import inspect file = self.file.removesuffix('.py') caller_scope = inspect.stack()[1].frame caller_scope.f_globals.update(__import__(file).__dict__) return self.file_as_str() threads = CodeSlide('threads.py') "from import *" in python command line instance, type threads to get the contents back and also import the files contents.