Imran, I don’t think this is a productive discussion. FWIW it's possible to implement all of Curio’s APIs on top of current asyncio: there are no fundamental blockers to that. If you think that Curio is better in some regards, please feel free to post concrete proposals to github.com/python/asyncio, let’s discuss. We’ve implemented 10s of proposals that added new APIs in the past few years.
Yury > On Oct 23, 2016, at 5:17 PM, Imran Geriskovan <[email protected]> > wrote: > > On 10/23/16, Guido van Rossum <[email protected]> wrote: >> Can you provide something more concrete, like a design for an API? > > I wont. But there is already a very good example. > >> So far it seems you're just complaining. Nobody likes that. > > There is no complaining. I'm already on my way. > Here, I'll respectfully aggree with anyone objecting any discussion > about any python async engine other than asyncio. That's > understandable. > >>> Providing direct async versions of blocking operations is the >>> key. That's it.
