classification
Title: optionxform documentation confusing
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: georg.brandl, loewis
Priority: normal Keywords:

Created on 2009-10-23 07:36 by loewis, last changed 2009-10-23 08:14 by georg.brandl. This issue is now closed.

Messages (2)
msg94375 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2009-10-23 07:36
In
http://stackoverflow.com/questions/1611799/preserve-case-in-configparser, somebody
is confused about adjusting ConfigParser.optionxform. The documentation
is indeed confusing, in particular by claiming that you should "set" it
to "str()". Even if you get what is meant by "setting" (i.e. not
"calling"), it's still nonsensical to suggest that it should be set to
an empty string.
msg94377 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-10-23 08:14
Thanks, fixed in r75623.
History
Date User Action Args
2009-10-23 08:14:54georg.brandlsetstatus: open -> closed
resolution: fixed
messages: + msg94377
2009-10-23 07:36:20loewiscreate