Miguel Grinberg   Asynchronous Python for the Complete Beginner   PyCon 2017

Miguel Grinberg Asynchronous Python for the Complete Beginner PyCon 2017

PyCon 2017

8 лет назад

124,912 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

@lator1941
@lator1941 - 30.03.2023 17:36

I read 5 articles and it wasn't until I watched this that I had deep understanding of the concept

Ответить
@youvanced6593
@youvanced6593 - 28.01.2023 22:36

Why can't I do web stuff with the multiprocessing library and what is the alternative? Let's say I computer that needs to run a python project that is both a Flask server and also does multiprocessing actions

Ответить
@shashishekhar----
@shashishekhar---- - 02.12.2022 19:08

You are awesome Miguel, seldom have I seen such complex things explained and put into perspective this easily, take care and god bless you and your family.

Ответить
@duongkstn
@duongkstn - 15.08.2022 18:30

thanks for sharing

Ответить
@malayagr
@malayagr - 14.08.2021 18:52

Didn't know Ben Kingsley wrote Python.

Ответить
@MarkusBurrer
@MarkusBurrer - 04.07.2021 15:33

Async doesn't make your code fast. It makes it just less idle

Ответить
@shreerangaraju1013
@shreerangaraju1013 - 22.06.2021 02:15

Brilliant analogy!

Ответить
@kellymoses8566
@kellymoses8566 - 24.05.2021 04:01

You don't really understand something until you can think of a really good analogy to explain it.

Ответить
@hairypaulsack
@hairypaulsack - 08.05.2021 15:46

1.25x

Ответить
@digiryde
@digiryde - 13.04.2021 05:04

I will never forget in my second year of comp sci classes in college (back when comp sci was the only computer class), my instructor told me (the class) that this was not asynchronous programming. And in the same breath that only MS was async. I have never forgotten what an idiot she was.

Ответить
@RajeshRRajamani
@RajeshRRajamani - 04.12.2020 09:52

I felt the chess analogy cleared my confusions here . Thank you so much .

Ответить
@experimentalhypothesis1137
@experimentalhypothesis1137 - 12.08.2020 12:11

miguel is a legend. i really like how humbly he speaks

Ответить
@driziiD
@driziiD - 23.03.2020 03:34

100% the chess example is hands-down the BEST possible example

Ответить
@juvewan
@juvewan - 05.03.2020 03:43

I fininally understand what Aysnc means. That chart comparing Process vs Thread vs Async is gold!

Ответить
@venkateshsrinivasan150
@venkateshsrinivasan150 - 05.08.2019 23:45

Brilliant talk!

Ответить
@XieQiu
@XieQiu - 04.06.2019 02:01

as a chess player i really appreciate the example.

Ответить
@mathematixal
@mathematixal - 04.05.2019 12:49

Wonderful overview of not only async but the advantages over multiprocess/multithread. It is good point that asyncio is designed to make you write/think in an async way.

Ответить
@ashu9sharma
@ashu9sharma - 21.04.2019 20:16

couldn't have explain it better :)

Ответить
@govardhangd9387
@govardhangd9387 - 12.03.2019 11:11

If asynchronous programming is just a style of concurrent programming, what are the other things that come under the umbrella of concurrent programming??? I thought this is the only way to do concurrent programming...

Ответить
@shamen2
@shamen2 - 06.02.2019 00:22

Excellent talk !!!

Ответить
@MaulinTolia
@MaulinTolia - 22.11.2018 16:54

Please give this man more time!

Ответить
@rohitbhanot7809
@rohitbhanot7809 - 20.11.2018 13:18

Threads arn't really any use if there are CPU bound tasks and hence GIL is an issue, but with async if GIL is not issue you can do concurrent CPU bound tasks, i think its an important he missed mentioning.

Ответить
@IsItTimeToTravel
@IsItTimeToTravel - 08.08.2018 12:49

This is how one should teach . That chess example is the best anyone could have given .

Ответить
@Johnged15
@Johnged15 - 12.07.2018 04:44

Appreciate this channel sharing this very informative content.

Ответить
@r3ap3rpy
@r3ap3rpy - 05.06.2018 09:55

Great talk!

Ответить
@ekbastu
@ekbastu - 01.06.2018 22:10

You rock :)

Ответить
@rickylim4910
@rickylim4910 - 02.05.2018 01:14

great talk, very straightforward as it is.

Ответить
@fuanka1724
@fuanka1724 - 01.04.2018 00:58

Thanks Miguel.

Ответить
@novie952
@novie952 - 18.01.2018 03:37

Very clear explanation !

Ответить
@SHUBHAMBHARDWAJBCE
@SHUBHAMBHARDWAJBCE - 28.11.2017 19:05

Can you please share the slides

Ответить
@arjunkirpal9776
@arjunkirpal9776 - 24.09.2017 12:30

Miguel Grinberg thanks.

Ответить
@vcool
@vcool - 02.09.2017 06:08

In summary, asyncio is great when at minimum you need thousands of concurrent executions in a process. Threads work for when you need mere hundreds at maximum, albeit with possible race conditions. Also, threaded programming is different and reasoning about it is different.

Ответить
@cosmicallyderived
@cosmicallyderived - 25.08.2017 01:34

This came up in the next recommended videos, and I wasn't particularly immediately interested in the topic as far as today was concerned (though I did have a todo interest for future review). But once I saw Miguel Grinberg was the speaker, I ponied up for the watch.

Ответить
@piyushkatariya1040
@piyushkatariya1040 - 24.08.2017 15:21

Always a good and clear talk. Thanks Miguel

Ответить
@nikitasid4947
@nikitasid4947 - 05.08.2017 20:27

Great! Thanks, Miguel.

Ответить
@temaz3334
@temaz3334 - 06.07.2017 15:33

Love Miguel teaching many years!

Ответить
@Ubben1999
@Ubben1999 - 20.06.2017 11:15

Reading Miguel's Flask book right now. He's a great writer, and apparently a pretty good speaker as well.

Ответить
@mrwibbles20
@mrwibbles20 - 18.06.2017 10:17

A good talk.

However, the gevent and eventlet examples were mismatched to the preceding "yield from" and "await" examples. Those used a loop to run the functions, which is the natural way to do it as it allows other functions to be also run asyncronously by that loop - hence the 10 call example with 10 hellos, followed by 10 worlds. The gevent and eventlet examples just called each single function in a non asynchronous way.. To be matching, they should have used the corresponding loop from those frameworks to similarly allow 10 versions of those functions to potentially be launched at the same time. The reason I mention this was the point that gevent and greenlet were harder to keep track of, as this omission served no purpose, other than to contrive this point a little.

Ответить
@jaroslawmichalski9021
@jaroslawmichalski9021 - 12.06.2017 18:26

so simple, but surprisingly good and very informative

Ответить
@wschmidt22
@wschmidt22 - 29.05.2017 05:14

Thought it was going to be about Flask.

Ответить
@andrealmar04
@andrealmar04 - 29.05.2017 04:40

very good talk. clear concepts and examples

Ответить
@fredrikaverpil
@fredrikaverpil - 23.05.2017 09:40

Very nice talk, cleared up a bunch of questions I had on asyncio.

Ответить