Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Selon "Martin v. Löwis" <[EMAIL PROTECTED]>: > > Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > > I don't understand the second loop (where n is given). If n is given, > there should be only a single read operation, using > > max(buffer_size, n-avail)
I mimicked the original logic rather than rethink the algorithm. I'm not totally sure what motivates the original logic but the purpose seems to be that non-blocking streams can return at least a few bytes rather than an empty string when less than N bytes are ready at OS level. > (i.e. the way it is in patch 2). In particular, if the stream is > unbuffered, it shouldn't ever end up with buffered data. Hmm, what do you mean by "if the stream is unbuffered"? Unbuffered streams should use the raw unbuffered objects (e.g. FileIO) rather than wrap them with BufferedReader. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2523> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
