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 pitrou
Recipients Dolda2000, benjamin.peterson, hynek, pitrou, python-dev, r.david.murray, serhiy.storchaka, stutzbach
Date 2013-12-27.17:01:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388163685.2298.5.camel@fsol>
In-reply-to <1388163266.97.0.950543744422.issue20074@psf.upfronthosting.co.za>
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?

A non-seekable read/write stream doesn't really make sense (think about
it).
What you may be thinking about, instead, is a pair of non-seekable
streams, one readable and one writable. There is BufferedRWPair for
that:
http://docs.python.org/dev/library/io.html#io.BufferedRWPair

(granted, BufferedRWPair isn't wired in open(), so you have to do all
the wrapping yourself)
History
Date User Action Args
2013-12-27 17:01:27pitrousetrecipients: + pitrou, benjamin.peterson, stutzbach, r.david.murray, python-dev, hynek, serhiy.storchaka, Dolda2000
2013-12-27 17:01:27pitroulinkissue20074 messages
2013-12-27 17:01:27pitroucreate