<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div>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.</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>Cheers,</div><div>Dave</div><div><br class=""></div><div><br class=""></div><div><blockquote type="cite" class=""><div dir="ltr" class=""><div class="">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.</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Sun, 6 Nov 2016 at 02:55 Cory Benfield <<a href="mailto:cory@lukasa.co.uk" class="">cory@lukasa.co.uk</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
> On 6 Nov 2016, at 00:09, Nathaniel Smith <<a href="mailto:njs@pobox.com" class="gmail_msg" target="_blank">njs@pobox.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> I just posted a long blog/essay that's probably of interest to folks here:<br class="gmail_msg">
><br class="gmail_msg">
> <a href="https://vorpus.org/blog/some-thoughts-on-asynchronous-api-design-in-a-post-asyncawait-world/" rel="noreferrer" class="gmail_msg" target="_blank">https://vorpus.org/blog/some-thoughts-on-asynchronous-api-design-in-a-post-asyncawait-world/</a><br class="gmail_msg">
><br class="gmail_msg">
> The short version: I think curio something important to teach us; I<br class="gmail_msg">
> tried to figure out what that is and how we can learn from it.<br class="gmail_msg">
<br class="gmail_msg">
This is a great post Nathaniel, and I think there’s a lot of value to extract from this for everyone.<br class="gmail_msg">
<br class="gmail_msg">
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. ;)<br class="gmail_msg">
<br class="gmail_msg">
Cory<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
Async-sig mailing list<br class="gmail_msg">
<a href="mailto:Async-sig@python.org" class="gmail_msg" target="_blank">Async-sig@python.org</a><br class="gmail_msg">
<a href="https://mail.python.org/mailman/listinfo/async-sig" rel="noreferrer" class="gmail_msg" target="_blank">https://mail.python.org/mailman/listinfo/async-sig</a><br class="gmail_msg">
Code of Conduct: <a href="https://www.python.org/psf/codeofconduct/" rel="noreferrer" class="gmail_msg" target="_blank">https://www.python.org/psf/codeofconduct/</a></blockquote></div>
_______________________________________________<br class="">Async-sig mailing list<br class=""><a href="mailto:Async-sig@python.org" class="">Async-sig@python.org</a><br class="">https://mail.python.org/mailman/listinfo/async-sig<br class="">Code of Conduct: https://www.python.org/psf/codeofconduct/</blockquote></div><br class=""></body></html>