[Async-sig] Some thoughts on asynchronous API design in a post-async/await world

David Beazley dave at dabeaz.com
Mon Nov 7 04:46:16 EST 2016

I don't know if curio (or something like it) is the future or not, but it is something that I'm building for myself so that I can use it. I like it.  It fits my brain.

I'd just like to reiterate Brett's comment about async/await being a protocol in Python and something that can be customized.  I don't know if that was by design or a happy accident, but so far as I can tell, it might be unique to Python.  Every other language that has this seems to have it pretty well locked down to a very specific runtime implementation involving callbacks and futures.   Python's approach allowed me to run with it in a completely different direction.  I think that's pretty neat.


> 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 at lukasa.co.uk <mailto:cory at lukasa.co.uk>> wrote:
> > On 6 Nov 2016, at 00:09, Nathaniel Smith <njs at pobox.com <mailto:njs at 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/ <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 at python.org <mailto:Async-sig at python.org>
> https://mail.python.org/mailman/listinfo/async-sig <https://mail.python.org/mailman/listinfo/async-sig>
> Code of Conduct: https://www.python.org/psf/codeofconduct/ <https://www.python.org/psf/codeofconduct/>_______________________________________________
> Async-sig mailing list
> Async-sig at python.org
> https://mail.python.org/mailman/listinfo/async-sig
> Code of Conduct: https://www.python.org/psf/codeofconduct/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/async-sig/attachments/20161107/7be90006/attachment-0001.html>

More information about the Async-sig mailing list