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-12.21:36:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373664975.69.0.746815023231.issue18430@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think the comment about save and restore of the file position adds enough value to be worth the possible confusion ("do I only need to save and restore around peek?  Why?")  I think the sentence should read, ex, "Calling a :class:`LZMAFile` object's :meth:`peek` method does not advance its access position, but the access position of the underlying :term:`file object` may be affected."

Note that I have no objection to making the two sync up, if it is in fact possible.  But if Serhiy says it can't be, I expect he's right.
History
Date User Action Args
2013-07-12 21:36:15r.david.murraysetrecipients: + r.david.murray, nadeem.vawda, serhiy.storchaka, madison.may, nbargnesi
2013-07-12 21:36:15r.david.murraysetmessageid: <1373664975.69.0.746815023231.issue18430@psf.upfronthosting.co.za>
2013-07-12 21:36:15r.david.murraylinkissue18430 messages
2013-07-12 21:36:15r.david.murraycreate