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 r.david.murray
Recipients Dolda2000, benjamin.peterson, hynek, pitrou, python-dev, r.david.murray, serhiy.storchaka, stutzbach
Date 2013-12-27.16:54:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388163266.97.0.950543744422.issue20074@psf.upfronthosting.co.za>
In-reply-to
Content
Having buffering doesn't make the stream seekable.  So the question is, is the *design* of the IO module that '+' requires a seekable stream the best behavior, or can that constraint be relaxed?  You have to keep in mind that the IO module is a bunch of building blocks, which are plugged together automatically for the most common scenarios.  The goal is a portable, consistent IO system, not one that completely mimics unix/C IO primitives.
History
Date User Action Args
2013-12-27 16:54:27r.david.murraysetrecipients: + r.david.murray, pitrou, benjamin.peterson, stutzbach, python-dev, hynek, serhiy.storchaka, Dolda2000
2013-12-27 16:54:26r.david.murraysetmessageid: <1388163266.97.0.950543744422.issue20074@psf.upfronthosting.co.za>
2013-12-27 16:54:26r.david.murraylinkissue20074 messages
2013-12-27 16:54:26r.david.murraycreate