➜

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.21:36:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388180172.28.0.105226049235.issue20074@psf.upfronthosting.co.za>
In-reply-to
Content 
Antoine already answered that question: it does not make sense to have a single stream that is open for *update* if it is not seekable.  The fact C conflates "update" with "both read and write" can be seen as a design bug in C :)
 
The remaining question might be: is there a sensible way (that fits with the design of the IO system) to hook BufferedRWPair up to open?
History
Date User Action Args
2013-12-27 21:36:12r.david.murraysetrecipients: + r.david.murray, pitrou, benjamin.peterson, stutzbach, python-dev, hynek, serhiy.storchaka, Dolda2000
2013-12-27 21:36:12r.david.murraysetmessageid: <1388180172.28.0.105226049235.issue20074@psf.upfronthosting.co.za>
2013-12-27 21:36:12r.david.murraylinkissue20074 messages
2013-12-27 21:36:12r.david.murraycreate