I would also like to thank everyone involved with defining async/await. I think the fact that async/await is an API and not something tightly bound to any specific event loop like in pretty much every other async-supporting language has been very beneficial to us and something to celebrate. The sheer fact that people who don't like asyncio, Twisted, Tornado, or curio have other options is fantastic._______________________________________________On Sun, 6 Nov 2016 at 02:55 Cory Benfield <cory@lukasa.co.uk> wrote:
> On 6 Nov 2016, at 00:09, Nathaniel Smith <njs@pobox.com> wrote:
>
> I just posted a long blog/essay that's probably of interest to folks here:
>
> https://vorpus.org/blog/some-thoughts-on-asynchronous-api-design-in-a-post-asyncawait-world/
>
> The short version: I think curio something important to teach us; I
> tried to figure out what that is and how we can learn from it.
This is a great post Nathaniel, and I think there’s a lot of value to extract from this for everyone.
In the short term, I’m going to address Twisted’s issue because it seems like the most glaring “this is a stupid bug” problem, and a quick glance at the relevant interfaces suggests it’s easily resolved. It also undermines my own personal mission to make Twisted a great HTTP/2 server. ;)
Cory
_______________________________________________
Async-sig mailing list
Async-sig@python.org
https://mail.python.org/mailman/listinfo/async-sig
Code of Conduct: https://www.python.org/psf/codeofconduct/
Async-sig mailing list
Async-sig@python.org
https://mail.python.org/mailman/listinfo/async-sig
Code of Conduct: https://www.python.org/psf/codeofconduct/