Guido van Rossum

Of course one thing to keep in mind is that the limit only applies to readline() and readuntil(). You can still use read() or readexactly() with arbitrary sizes. For the...

BTW, I'm glad that we've at least arrived at the same convention as aiohttp for .readuntil(stop): it returns the data including the delimiter ( http://aiohttp.readthedocs.org/en/stable/_modules/aiohttp/parsers.html#ParserBuffer.readuntil ). I still think it's...

Interesting. I spent some time tracing through this code and haven't gotten further than observing that if you change the `read(-1)` in the _server_ to `read(1000)` things work as expected....

OK, I think I found it. StreamReaderProtocol.eof_received() should return True to keep the transport open even after receiving an EOF. I've filed a bug in the Python tracker: http://bugs.python.org/issue24539

The fix is in https://github.com/python/asyncio/commit/ce3ad816a2ef9456b4b1c26b99dfc85ea1236811 but I'm keeping this issue (and the CPython issue) open because it needs a test and merging into CPython.

It's now still open because (1) there's still no test AFAIK, and (2) the fix elicits a warning for SSL streams because those don't support write_eof().

Definitely 3.7. Until then this could easily be implemented as a separate AbstractServer subclass.

For something meant to go into the stdlib at 3.7, copypasta is probaby not a problem.

(Notice: I'm all out of round tuits today.)

I can repro this too -- it's not unique to Windows or to PEP 492 (it fails the same way with coroutine/yield-from in Python 3.4). It's also not due to...