9:07 I have wondered about constructs like async def myfunc ... : return await «expr» which could be simplified to def myfunc ... : return «expr» Given that the caller expects an awaitable in either case, the behaviour is exactly the same.
1. get_nowait() raises queue.Empty exception. How do you handle that? I don't see 2. In that case there will be raised exception from future in run_until_complete which will lead to terminating all application
Yes, I elided the exception handling in the slides for the sake of brevity, but the code in the aiomultiprocess library correctly handles the Empty exceptions. See github.com/jreese/aiomultiprocess/blob/master/aiomultiprocess/core.py for more details.
I really wish speakers would learn a bit more about speaking or practice for an objective listener (for feedback) before presenting. I know nerves can be a factor, but constant "ums" and "uhs" can really detract from a presentation. This was hard for me to watch as a result of that.
I really wish TH-cam commenters would learn a bit more about communication or practice with an objective reader (for feedback) before commenting. I know they're just trying to give advice, but the condescending tone and odd passive aggressiveness can really distract from the message. This comment was hard to read as a result of that.
Well, yeah, is it possible that you don't understand the topic well enough to follow so you focused on the style of presentation rather than the content? Surely it wasn't exceptionally entertaining but totally fine and with high quality information. Didn't really notice the "ums" until reading your comment. You could be a bit more thankful for being provided with quality information for free.
This video became a gold mine for me
at @5:55 , you know he is a great programmer when he says, his coworker 'JSON'.
awesome video! I am looking forward to trying this out with AsyncSSH
8:25 multiprocessing supports shared storage, but you cannot put arbitrary Python objects here, only ctypes objects.
This is great, thanks!
9:07 I have wondered about constructs like
async def myfunc ... :
return await «expr»
which could be simplified to
def myfunc ... :
return «expr»
Given that the caller expects an awaitable in either case, the behaviour is exactly the same.
great video well done
As usual the links to both the slides and speakerdeck point to nothing! Please fix this.
1. get_nowait() raises queue.Empty exception. How do you handle that? I don't see
2. In that case there will be raised exception from future in run_until_complete which will lead to terminating all application
Yes, I elided the exception handling in the slides for the sake of brevity, but the code in the aiomultiprocess library correctly handles the Empty exceptions. See github.com/jreese/aiomultiprocess/blob/master/aiomultiprocess/core.py for more details.
Can someone tell me what font he is using for his code, for example at 2:43 there?
Probably Hack: github.com/source-foundry/Hack
It's Fira Code: github.com/tonsky/FiraCode
11:25
Great library, well done! Just relax and learn to speak in public
Hmm... i look this
Why jumping through so many hoops to use Python instead of using a better programming language?
Define "better"
I sense a straggler from the Java/C♯/PHP crowd ...
I really wish speakers would learn a bit more about speaking or practice for an objective listener (for feedback) before presenting. I know nerves can be a factor, but constant "ums" and "uhs" can really detract from a presentation. This was hard for me to watch as a result of that.
I haven't noticed this until reading your comment!
I really wish TH-cam commenters would learn a bit more about communication or practice with an objective reader (for feedback) before commenting. I know they're just trying to give advice, but the condescending tone and odd passive aggressiveness can really distract from the message. This comment was hard to read as a result of that.
Well, yeah, is it possible that you don't understand the topic well enough to follow so you focused on the style of presentation rather than the content? Surely it wasn't exceptionally entertaining but totally fine and with high quality information. Didn't really notice the "ums" until reading your comment. You could be a bit more thankful for being provided with quality information for free.