Message258617
After taking a little time to let this sink in, I'm going to play Devil's Advocate just a little more.
It sounds like you're basically saying that any read-write text-based modes (e.g. r+, w+) should be used at your own peril. While I understand your UTF-7 counterexample, and it's a fair point, is it out of line to expect that for encodings that operate on full bytes, file positioning should work a bit more intuitively? (Which is to say, a write/truncate after a read should take place in the position immediately following the end of the read.) |
|
Date |
User |
Action |
Args |
2016-01-19 19:24:28 | fornax | set | recipients:
+ fornax, pitrou, vstinner, benjamin.peterson, stutzbach, Zero, docs@python, serhiy.storchaka, eryksun, steve.dower |
2016-01-19 19:24:28 | fornax | set | messageid: <1453231468.23.0.121999934745.issue26158@psf.upfronthosting.co.za> |
2016-01-19 19:24:28 | fornax | link | issue26158 messages |
2016-01-19 19:24:27 | fornax | create | |
|