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 bakuriu
Recipients arigo, bakuriu, benjamin.peterson, brian.curtin, catalin.iacob, pitrou, rhettinger, serhiy.storchaka, skrah
Date 2013-04-11.20:40:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365712816.74.0.518295520775.issue16273@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation for python 3.3.1 states, at http://docs.python.org/3/tutorial/inputoutput.html#reading-and-writing-files, states:

    f.tell() returns an integer giving the file object’s current position in the file, **measured in bytes from the beginning of the file**.

And regarding files opened in text mode the only statement is:

    In text files (those opened without a b in the mode string), only seeks relative to the beginning of the file are allowed (the exception being seeking to the very file end with seek(0, 2)).

Even though in the io module it is documented that it may not be the number of bytes.

I think the former documentation should be changed, since it's simply wrong. Sorry for the disturb, but in the beginning I thought it was related.
History
Date User Action Args
2013-04-11 20:40:16bakuriusetrecipients: + bakuriu, arigo, rhettinger, pitrou, benjamin.peterson, brian.curtin, skrah, catalin.iacob, serhiy.storchaka
2013-04-11 20:40:16bakuriusetmessageid: <1365712816.74.0.518295520775.issue16273@psf.upfronthosting.co.za>
2013-04-11 20:40:16bakuriulinkissue16273 messages
2013-04-11 20:40:16bakuriucreate