[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Changes by Łukasz Langa : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Changes by Éric Araujo : -- status: closed -> pending title: ConfigParser. -> ConfigParser.[Raw]ConfigParser optionxform() ___ Python tracker ___

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Georg Brandl added the comment: The point is, all gratuitous changes to such branches are a nuisance to the release manager who decides what needs to go into a security release. Also, doc changes in 2.6 are almost completely gratuitous, since the docs are never again built and put online some

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Łukasz Langa added the comment: Sorry about that. Since I'm not technically touching the source code, I thought the security fixes restriction does not necessarily apply. Especially that my patch only updates what ends up here: http://docs.python.org/release/2.6.6/library/configparser.html -

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Éric Araujo added the comment: 2.5 and 2.6 are in security mode. Other bug fixes, build changes, documentation improvements, etc. should not go in these branches. Your commit does not break anything, but for process clarity, please back it out. -- nosy: +eric.araujo ___

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Changes by Łukasz Langa : -- versions: +Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Roundup Robot added the comment: New changeset c7ce67c9237a by Łukasz Langa in branch '2.6': Closes #11786: ConfigParser.[Raw]ConfigParser optionxform(). http://hg.python.org/cpython/rev/c7ce67c9237a New changeset a6b772599594 by Łukasz Langa in branch '2.7': Merged solution for #11786 from 2.6

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Łukasz Langa added the comment: The documentation may be poorly worded but `optionxform()` has always been used also by RawConfigParser. It has been that way since the introduction of this class in Python 2.3 (previously there was only one ConfigParser class which used `optionxform()` since a

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

Changes by Łukasz Langa : -- assignee: docs@python -> lukasz.langa nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mai

[issue11786] ConfigParser.[Raw]ConfigParser optionxform()

New submission from Adam Groszer : The documentation http://docs.python.org/library/configparser.html states that optionxform() is used only beginning ConfigParser.ConfigParser, whereas it is ALSO in effect for ConfigParser.RawConfigParser. (As I checked in the source) -- assignee: doc