➜

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 Rich.Rauenzahn
Recipients Rich.Rauenzahn, lukasz.langa, xiang.zhang
Date 2016-06-19.05:16:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466313361.37.0.519043910977.issue27351@psf.upfronthosting.co.za>
In-reply-to
Content 
Given that write() accepts a fileobject, but read() accepts a list of strings or a string (and readfp() is the one that accepts a fileobject instead), this seems like it could be a common enough error that just iterating over the fileobject could be undesirable and an exception might be thrown instead.

I'm throwing this out here to see if the library maintainers were aware of this odd edge case.
History
Date User Action Args
2016-06-19 05:16:01Rich.Rauenzahnsetrecipients: + Rich.Rauenzahn, lukasz.langa, xiang.zhang
2016-06-19 05:16:01Rich.Rauenzahnsetmessageid: <1466313361.37.0.519043910977.issue27351@psf.upfronthosting.co.za>
2016-06-19 05:16:01Rich.Rauenzahnlinkissue27351 messages
2016-06-19 05:16:01Rich.Rauenzahncreate