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 famart
Recipients cassava, famart, ocean-city, pitrou, r_mosaic
Date 2009-07-31.21:38:54
SpamBayes Score 2.3910525e-06
Marked as misclassified No
Message-id <1249076335.99.0.162087180462.issue5505@psf.upfronthosting.co.za>
In-reply-to
Content
Looks like python needs eof() or something for file objects, just like
any other languages.

Since read() is using the system call, that's the right behavior: read()
blocks until EOF, and returns whatever was buffered. EOF character is
consumed, but since it's a stdin, it is never closed. The next read()
will again wait for normal input.

The 2nd EOF mark without anything in-between will return an empty string.
History
Date User Action Args
2009-07-31 21:38:56famartsetrecipients: + famart, pitrou, ocean-city, r_mosaic, cassava
2009-07-31 21:38:55famartsetmessageid: <1249076335.99.0.162087180462.issue5505@psf.upfronthosting.co.za>
2009-07-31 21:38:54famartlinkissue5505 messages
2009-07-31 21:38:54famartcreate