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

> On Nov 7, 2016, at 11:58 AM, Guido van Rossum wrote: > > I would caution against rushing into anything rash here. Nathaniel's post > will stand as one of the most influential posts (about async I/O in Python) > of this generation, and curio is a beacon of clarity compared

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

Maybe we need couple other coroutines: 1. asyncio.run_in_executor() 2. asyncio.create_task(). Yes, ensure_future() does the same job but the name is confusing. At least it is confusing for my training course attendees. Also the are unfortunately tries to use `asyncio.wait()` because the name is

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

> On Nov 7, 2016, at 11:08 AM, Yury Selivanov wrote: > > [..] >> Sorry, this was a bit tongue in cheek. This was something I said to Guido >> at the *very* beginning of Tulip development, when asked about mistakes >> Twisted has made: "don't have a global event loop,

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

[..] > Sorry, this was a bit tongue in cheek. This was something I said to Guido at > the *very* beginning of Tulip development, when asked about mistakes Twisted > has made: "don't have a global event loop, you'll never get away from it". > > I still think getting rid of a global loop would

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

> On Nov 7, 2016, at 12:50 PM, Brett Cannon wrote: > > > > On Sun, 6 Nov 2016 at 22:41 Glyph Lefkowitz wrote: > >> On Nov 6, 2016, at 8:20 PM, Brett Cannon wrote: >> >> For me there are two questions the post raises. One is how

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

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.