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 yavuz164
Recipients yavuz164
Date 2008-12-11.15:31:14
SpamBayes Score 0.00021218907
Marked as misclassified No
Message-id <1229009477.19.0.97866751034.issue4633@psf.upfronthosting.co.za>
In-reply-to
Content
I find that file.tell returns not the byte offset of the next byte, but
possibly the byte offset of the next block to be read. I find it always
to be a multiple of 1024. Following is a demo of the bug. where I read a
 few lines into a text file, step back by the length of the last read
line, read again, and do not find the same data. What is returned is the
tail part of a line way down  in the file. I woeked around by keeping
track of the file pointer, and seek worked fine. tell() is at fault.
----------demonstration on a text file
Python 2.5.1 (r251:54863, Nov 14 2007, 16:00:54) 
[GCC 3.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> jf=open('junk','r')
>>> line=jf.next()
>>> line
'\n'
>>> line=jf.next()
>>> line
'See COPYING file in the same directory as this one for license.\n'
>>> line=jf.next()
>>> line
'\n'
>>> line=jf.next()
>>> line
'Thank you for trying this utility. I had great fun putting it\n'
>>> line=jf.next()
>>> line
'together, and I hope users will find it useful.\n'
>>> jf.seek(len(line),1)
>>> line=jf.next()
>>> line
'gle says Maps will not work without it. file:// URLs are \n'
History
Date User Action Args
2008-12-11 15:31:17yavuz164setrecipients: + yavuz164
2008-12-11 15:31:17yavuz164setmessageid: <1229009477.19.0.97866751034.issue4633@psf.upfronthosting.co.za>
2008-12-11 15:31:16yavuz164linkissue4633 messages
2008-12-11 15:31:14yavuz164create