This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients benjamin.peterson, neologix, petri.lehtinen, pitrou, sbt, stutzbach
Date 2011-11-04.19:38:37
SpamBayes Score 3.6318e-08
Marked as misclassified No
Message-id <1320435249.3379.3.camel@localhost.localdomain>
In-reply-to <>
> >> But what about the buggy readline() behaviour?
> > Just tell people that if the return value is a string which does not 
> > end in '\n' then it might caused by EOF or EAGAIN.  They can just call 
> > readline() again to check which.
> Sounds reasonable.

But then what's the point of using buffered I/O at all? If it can't
offer anything more than raw I/O, I'd rather do something like raise a
RuntimeError("buffered I/O doesn't work with non-blocking streams") when
the raw stream returns None. Returning partial results on a buffered's
readline() is not something we should ever do.

(actually, raw I/O readline() is probably buggy as well)
Date User Action Args
2011-11-04 19:38:38pitrousetrecipients: + pitrou, benjamin.peterson, stutzbach, neologix, sbt, petri.lehtinen
2011-11-04 19:38:37pitroulinkissue13322 messages
2011-11-04 19:38:37pitroucreate