Guido van Rossum

@achimnol I am fine with adding `asyncio.create_task()`. By the time we are ready to talk about it we should have no problem explain what a task is and what its...

Tasks and coroutines are different! They should not be confused. A coroutine is simply a function defined with `async def`. Coroutines can be used for different frameworks, but it's usually...

It would be hugely backward compatible. It would also be a huge bug magnet -- diagnostics if you forget to await the close() call are minimal.

That was about making close() a coroutine.

But what is the failure mode if you don't use wait_closed()? The stream _does_ get closed, just on the next trip through the loop, right?

OK, but unittests are different from regular apps. They can await s.wait_closed(). Also, if close() became a coroutine, calling it without waiting for it would do _nothing_ -- the body...

Please, no. There are many close() methods and it would be confusing which return a Future and which don't.

Please rally support on the mailing list: https://groups.google.com/forum/?fromgroups#!forum/python-tulip

Sure, add this. I don't have time for a review though.

So forever is just sleep infinity? Why do we need that? --Guido (mobile)