Gregory P. Smith <[EMAIL PROTECTED]> added the comment: I agree with Amuary, write() traditionally never writes less data unless the underlying IO is in nonblocking mode.
I'm working up a new patch to write to self.raw in max_buffer_size chunks with as few data copies as possible, raising an appropriate BlockingIOError (as the surrounding code does) when the IO on the underlying self.raw.write raises one through self._flush_unlocked(). _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4428> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
