> On Oct 24, 2016, at 12:38 PM, Xavier Combelle <[email protected]> > wrote: > > >> Yes, this is something that has to be fixed in asyncio docs. >> Protocols/transports are advanced low level concepts, you don’t need to even >> know about them to use asyncio programs. I’ll try to find some time to work >> on the docs before 3.6 is released... >> >> Yury >> > > If I don't mistake, that is the high level api > https://docs.python.org/3.6/library/asyncio-stream.html#tcp-echo-client-using-streams > looks like the api is different than sync ones (with notably one reader and > one writer) and that the loop is needed everywhere
Right, passing the “loop” explicitly is another point to fix in the docs. Short answer - don’t do that in your programs. You might want to pass the loop explicitly when you’re working on a reusable library like aiohttp, but that’s about it. We also can have a third-party package that would implement curio-like stream object and socket object if a lot of people think it’s easier to work with. This is something that can be easily addressed even with the current asyncio. Yury
