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 martin.panter
Recipients Zero, benjamin.peterson, docs@python, eryksun, fornax, martin.panter, pitrou, serhiy.storchaka, steve.dower, stutzbach, vstinner
Date 2016-01-19.21:38:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453239509.64.0.993822204527.issue26158@psf.upfronthosting.co.za>
In-reply-to
Content
In theory, TextIOWrapper could rewrite the last bit of the file (or the whole file) to have the requested number of characters. But I wonder if it is worth it; maybe deprecation is better. Do you have a use case for any of these bugs, or are you just playing around to see what the methods do?

In Issue 12922, seek() and tell() were (re-)defined for TextIOBase, but the situation with truncate() was apparently not considered.

Perhaps the write()–read() bug is related to Issue 12215.
History
Date User Action Args
2016-01-19 21:38:29martin.pantersetrecipients: + martin.panter, pitrou, vstinner, benjamin.peterson, stutzbach, Zero, docs@python, serhiy.storchaka, eryksun, steve.dower, fornax
2016-01-19 21:38:29martin.pantersetmessageid: <1453239509.64.0.993822204527.issue26158@psf.upfronthosting.co.za>
2016-01-19 21:38:29martin.panterlinkissue26158 messages
2016-01-19 21:38:29martin.pantercreate