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

[George Fischhof]

George Fischhof added the comment:

Hi,

issue 28788 created as feature request

BR,
George

--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[R. David Murray]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[George Fischhof]

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 create file with invalid content (for example 
(this was my findings) creates duplicated sections.

So it could be a feature request for ConfigParser:
It should be able to write config to a given filename, not only into file 
object.
(Like xml parser)

Kind regards,
George

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Berker Peksag]

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

--
nosy: +berker.peksag

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[George Fischhof]

Changes by George Fischhof :


--
title: Addition to Documentation of configparser.ConfigParser.write() 
documentaion -> Addition to Documentation of configparser.ConfigParser.write()

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[George Fischhof]

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 issued a file.seek(0) command before write and the result was good.


So I think documentaion should advice to user to reopen the file with mode 'w' 
or to issue a file.seek(0) command before using the ConfigParser.write()


I used the following python version on windows:
Python 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:38:48) [MSC v.1900 32 bit 
(Intel)] on win32

affected documentation:
https://docs.python.org/3.5/library/configparser.html#configparser.ConfigParser.write

Best Regards,
George Fischhof

--
assignee: docs@python
components: Documentation
messages: 280960
nosy: docs@python, georgefischhof
priority: normal
severity: normal
status: open
title: Addition to Documentation of configparser.ConfigParser.write() 
documentaion
versions: Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com