Changes by Łukasz Langa luk...@langa.pl:
--
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11786
___
___
Python-bugs-list
Changes by Éric Araujo mer...@netwok.org:
--
status: closed - pending
title: ConfigParser. - ConfigParser.[Raw]ConfigParser optionxform()
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11786
Georg Brandl ge...@python.org 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
Éric Araujo mer...@netwok.org 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:
Łukasz Langa luk...@langa.pl 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:
Roundup Robot devnull@devnull 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
Changes by Łukasz Langa luk...@langa.pl:
--
versions: +Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11786
___
___
Python-bugs-list
New submission from Adam Groszer agros...@gmail.com:
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)
Changes by Łukasz Langa luk...@langa.pl:
--
assignee: docs@python - lukasz.langa
nosy: +lukasz.langa
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11786
___
Łukasz Langa luk...@langa.pl 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
10 matches
Mail list logo
