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 fornax
Recipients Zero, benjamin.peterson, docs@python, eryksun, fornax, martin.panter, pitrou, serhiy.storchaka, steve.dower, stutzbach, vstinner
Date 2016-01-19.21:56:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453240582.63.0.000511414294997.issue26158@psf.upfronthosting.co.za>
In-reply-to
Content
I don't have a specific use case. This spawned from a tangentially-related StackOverflow question (http://stackoverflow.com/questions/34858088), where in the answers a behavior difference between Python 2 and 3 was noted. I couldn't find any documentation to explain it, so I opened a follow-up question (http://stackoverflow.com/questions/34879318), and based on some feedback I got there, I opened up this issue.

Just to be sure I understand, you're suggesting deprecating truncate on text-mode file objects? And the interleaved read-writes are likely related to an issue that will be dealt with elsewhere?
History
Date User Action Args
2016-01-19 21:56:22fornaxsetrecipients: + fornax, pitrou, vstinner, benjamin.peterson, stutzbach, Zero, docs@python, martin.panter, serhiy.storchaka, eryksun, steve.dower
2016-01-19 21:56:22fornaxsetmessageid: <1453240582.63.0.000511414294997.issue26158@psf.upfronthosting.co.za>
2016-01-19 21:56:22fornaxlinkissue26158 messages
2016-01-19 21:56:22fornaxcreate