Comments on: Bizarre Python File Error http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/ Random notes about software development Tue, 31 Jan 2012 20:59:33 +0000 hourly 1 http://wordpress.com/ By: John http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/#comment-126 Thu, 25 Nov 2010 00:20:03 +0000 http://jotnotes.wordpress.com/?p=32#comment-126 Thanks for writing about this bug! You saved me a lot of time. :)

many thanks.

]]> By: Ron McLaren http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/#comment-107 Mon, 01 Nov 2010 15:09:45 +0000 http://jotnotes.wordpress.com/?p=32#comment-107 You need to move the file pointer to the insertion point of the write. Just do f.seek(0) to move the file pointer back to the beginning…

]]> By: ahmet alp balkan http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/#comment-62 Fri, 02 Jul 2010 23:52:02 +0000 http://jotnotes.wordpress.com/?p=32#comment-62 Most probably the problem causes from r+ mode. If you separate read stream and write stream, problem is solved.

]]> By: ahmet alp balkan http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/#comment-61 Fri, 02 Jul 2010 23:48:36 +0000 http://jotnotes.wordpress.com/?p=32#comment-61 I’ve experienced the same bug today on python 2.6.5.12 32-bit.

I think there is something underneath causes this problem. Error message is not descriptive. Maybe the problem is I’ve created file at just under c:\ folder. there may be UAC restrictions… I’ll post here again when I find a soln. Please contact me if you find any, too.

]]> By: Colin Howell http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/#comment-57 Mon, 19 Apr 2010 04:31:04 +0000 http://jotnotes.wordpress.com/?p=32#comment-57 Just ran into this myself. It seems to be a general problem with Python 2.x on Windows when doing interleaved reads and writes on a file which has been opened in a “+” mode. It’s caused by the behavior of the underlying C library. The general workaround is to insert a flush() or seek() operation when switching between reading and writing.

Python 3.x doesn’t have this problem, because the underlying I/O implementation was changed.

See the following bug reports:

http://bugs.python.org/issue3207
http://bugs.python.org/issue1636874

]]> By: uszy wieloryba http://blog.myjotnotes.com/2008/07/08/bizarre-python-file-error/#comment-50 Mon, 09 Nov 2009 20:15:59 +0000 http://jotnotes.wordpress.com/?p=32#comment-50 I have experienced the same problem.

Thanks for the workaround.

]]>