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 wolma
Recipients lukasz.langa, r.david.murray, rk, wolma
Date 2016-11-19.21:38:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479591482.28.0.413185704907.issue27583@psf.upfronthosting.co.za>
In-reply-to
Content
Well, you *can* change the value at runtime as you are demonstrating in your script, but you are misunderstanding the effect this will have. It *won't* cause a reevaluation of an already parsed config file. Instead it will affect the writing of the parsed settings to a new config file.
This is explained a bit further up in the documentation of the module:
https://docs.python.org/3/library/configparser.html#customizing-parser-behaviour
where it says: "Its current value can be retrieved using the parser_instance.default_section attribute and may be modified at runtime (i.e. to convert files from one format to another)."

So maybe this hint could be repeated in the actual parameter description of https://docs.python.org/3/library/configparser.html#configparser-objects to avoid confusion, but I don't think there is a bug here.
History
Date User Action Args
2016-11-19 21:38:02wolmasetrecipients: + wolma, r.david.murray, lukasz.langa, rk
2016-11-19 21:38:02wolmasetmessageid: <1479591482.28.0.413185704907.issue27583@psf.upfronthosting.co.za>
2016-11-19 21:38:02wolmalinkissue27583 messages
2016-11-19 21:38:01wolmacreate