code review link: https://codereview.appspot.com/60060044

Thanks! I put some review comments on Rietveld. (It's easy to download the 
patch from Rietveld, so no need to separately attach the patch. Just use 
upload.py -i to add your new version to Rietveld.)

Guido, there is a new patch on Rietveld, please take a look when you have a 
time.

Fixed in ad6c4676f809

I also see that you added StreamReader.at_eof() method, what is the use case 
for such method?

See https://code.google.com/p/tulip/issues/detail?id=101&can=1

Oh, reminder. When a commit fixes an issue, the commit message should mention 
the issue#. With the right syntax (I think "fix issue #NNN") it'll 
automatically include the commit in the issue.

NP

For some reason I thought google code does not support this feature.
What's the protocol for committing back to cpython? Should a proxy issue on 
bugs.python.org be created, or we can simply put a url to google code issue?

I've done neither so far -- I just prefix the commit message with "asyncio:" 
and assume people will figure out to compare the change logs in cpython with 
those in the Tulip repo (which I consider upstream). Oh, and every once in a 
while I trawl the logs and add a mass NEWS item. Nothing too formal.