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 madison.may, nadeem.vawda, nbargnesi, r.david.murray, serhiy.storchaka
Date 2013-07-11.20:26:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373574396.15.0.698916616133.issue18430@psf.upfronthosting.co.za>
In-reply-to
Content
Regardless of whether or not it *can* be fixed, I personally would not expect the file position to be either unchanged or predictable.  The file object is being passed to something that is going to read and/or write from it, after all.  If the calling application needs the file to be in a particular seek position, it should save it and reset it, I think.
History
Date User Action Args
2013-07-11 20:26:36r.david.murraysetrecipients: + r.david.murray, nadeem.vawda, serhiy.storchaka, madison.may, nbargnesi
2013-07-11 20:26:36r.david.murraysetmessageid: <1373574396.15.0.698916616133.issue18430@psf.upfronthosting.co.za>
2013-07-11 20:26:36r.david.murraylinkissue18430 messages
2013-07-11 20:26:36r.david.murraycreate