On 7/2/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > Honestly, I think truncate() should always set the current position to > the new size, even though that's not what it currently does. Or at > least it should set it to the new size if that's less than the current > position. What's the rationale (apart from "Unix defined it so") why > it currently leaves the position unchanged?
No idea. I just know that truncate in the old StringIO module do set the position to the new size if the new size is less than the current position. And that is how I implemented it in _bytes_io and _string_io. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
