Re: [Async-sig] Inadvertent layering of synchronous code as frameworks adopt asyncio

> As for jupyter, I think the best thing for them to do is run all notebook > user code in a separate thread dedicated to that purpose, and hide the fact > that the notebook itself is running asyncio as much as possible. That user > thread can start up its own event loop if it wants, but that's

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

> 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,