On 2/28/07, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: > >On EOF, they return a length-0 object or 0 instead. If the user tries > >to read again *after* hitting EOF, then an EOFError is raised. > > What is the motivation for having two different ways to signal EOF? How > is this case handled?
I checked how Python 2.5 handles this, and you're right. Read operations should continue to return 0 bytes if the user keeps trying to read at EOF. Not sure what I was thinking. -- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises LLC _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
