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 berker.peksag
Recipients berker.peksag, docs@python, georgefischhof
Date 2016-11-23.16:18:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479917939.46.0.651580349303.issue28714@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the report, George.

Using 'r+' means that you don't have to reopen the same file if you want to both read and write to it but it's up to you to check where the cursor is before writing anything to it.

Since the ConfigParser.write() method doesn't have any control over the file object (and this is not the only place that someone can pass a file object in the stdlib), I don't think we should make its documentation more complicated.

I wouldn't strongly object adding a short sentence about the behavior of the + mode if someone wants to write a patch. Doc/tutorial/inputoutput.rst or Doc/library/functions.rst might be a good place to put that information.
History
Date User Action Args
2016-11-23 16:18:59berker.peksagsetrecipients: + berker.peksag, docs@python, georgefischhof
2016-11-23 16:18:59berker.peksagsetmessageid: <1479917939.46.0.651580349303.issue28714@psf.upfronthosting.co.za>
2016-11-23 16:18:59berker.peksaglinkissue28714 messages
2016-11-23 16:18:58berker.peksagcreate