[issue5541] File's current position inconsistent with 'a+' mode

["Martin v. Löwis" <report@bugs.python.org> at psf.upfronthosting.co.za]

Martin v. Löwis <martin at v.loewis.de> added the comment:

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".

----------
nosy: +loewis
resolution:  -> wont fix
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5541>
_______________________________________