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 loewis
Recipients ebfe, loewis, pitrou
Date 2009-03-23.21:01:24
SpamBayes Score 4.6528644e-06
Marked as misclassified No
Message-id <1237842090.8.0.318090772364.issue5541@psf.upfronthosting.co.za>
In-reply-to
Content
In 2.x, the mode will do whatever the C library does; this is as it
ought to be. Standard C lets it explicitly implementation-defined
whether the file position pointer is initially at the beginning or at
the end of a file when the file is opened for append. Any write
operating will automatically move the file pointer to the end of the
file; switching between reading and writing must be synchronized with
either a flush operation or a file positioning operation.

So I'm closing this as "won't fix".
History
Date User Action Args
2009-03-23 21:01:30loewissetrecipients: + loewis, pitrou, ebfe
2009-03-23 21:01:30loewissetmessageid: <1237842090.8.0.318090772364.issue5541@psf.upfronthosting.co.za>
2009-03-23 21:01:25loewislinkissue5541 messages
2009-03-23 21:01:24loewiscreate