Antoine Pitrou <pit...@free.fr> added the comment:
> >> 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)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13322>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
