Why were some keywords added in Python for Async/Await when the concurrency model could have been implemented as functions in a separate library (loosely coupled), which is done by some programming languages ( ua-cam.com/video/XEgibiHdJtQ/v-deo.html )?
Isn't it a little unfair to downplay curio and trio because they're "not mainstream," yet hype up tokio, a more nascent library that hinges on integration with a completely different - and admittedly not mainstream - programming language? To my eyes, tokio carries more risk as a project than curio or trio. tokio is an exciting, interesting project, however let's give a little more respect to Python's "mad scientist", David Beazley, for demonstrating via implementation that a *pure Python* async framework can involve less complexity than asyncio, and give better performance.
I do like curio a lot, but I would recommend trio as a more "secure" alternative since curio is clearly somewhat of a playground to Beazley and its README still clearly claims it is experimental and only supports Unix systems. In 3.7 asyncio is also much more usable and well documented as well.
Another great talk, Yuri. 👍
Great to see the PythonRust integration!
Why were some keywords added in Python for Async/Await when the concurrency model could have been implemented as functions in a separate library (loosely coupled), which is done by some programming languages ( ua-cam.com/video/XEgibiHdJtQ/v-deo.html )?
After listening this talk I still dont know what async/await actually IS.
I still don’t know how use async/await in python...
Isn't it a little unfair to downplay curio and trio because they're "not mainstream," yet hype up tokio, a more nascent library that hinges on integration with a completely different - and admittedly not mainstream - programming language? To my eyes, tokio carries more risk as a project than curio or trio.
tokio is an exciting, interesting project, however let's give a little more respect to Python's "mad scientist", David Beazley, for demonstrating via implementation that a *pure Python* async framework can involve less complexity than asyncio, and give better performance.
I do like curio a lot, but I would recommend trio as a more "secure" alternative since curio is clearly somewhat of a playground to Beazley and its README still clearly claims it is experimental and only supports Unix systems. In 3.7 asyncio is also much more usable and well documented as well.
4:11 something else that’s missing: being able to asynchronously assign a new value to a property, e.g. something like
await obj.prop = value
When would we need this? Only case I can think of is:
obj.prop = await value
which is already done.