[issue28714] Addition to Documentation of configparser.ConfigParser.write()

George Fischhof added the comment: Hi, issue 28788 created as feature request BR, George -- status: open -> closed ___ Python tracker ___ __

[issue28714] Addition to Documentation of configparser.ConfigParser.write()

R. David Murray added the comment: That would be a separate issue (a feature request). It would make sense, since there is already a read_file method. -- nosy: +r.david.murray ___ Python tracker _

[issue28714] Addition to Documentation of configparser.ConfigParser.write()

George Fischhof added the comment: Hi Berker, It is true, I agree ;-) But this way ConfigParser works different than xml parsers (for example elementtree from system lib), as when I use elementtree.write it wil create a file with full and valid xml content. But ConfigParser is "able" ;-) to

[issue28714] Addition to Documentation of configparser.ConfigParser.write()

Berker Peksag added the comment: 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 ha

[issue28714] Addition to Documentation of configparser.ConfigParser.write()

Changes by George Fischhof : -- title: Addition to Documentation of configparser.ConfigParser.write() documentaion -> Addition to Documentation of configparser.ConfigParser.write() ___ Python tracker _

[issue28714] Addition to Documentation of configparser.ConfigParser.write() documentaion

New submission from George Fischhof: Hi There, I used configparser.ConfigParser.write() to update a config file. And I found that my config wa duplicated. The file was opened with mode 'r+' I figured out that write (I mean the write method of configparser) writes at actual file position. I