configglue team mailing list archive
-
configglue team
-
Mailing list archive
-
Message #00027
[Bug 677108] [NEW] Use ConfigParser.SafeConfigParser instead of the broken ConfigParser.ConfigParser
Public bug reported:
ConfigParser.ConfigParser is broken in terms of interpolation
completeness. It also lets users set() non-string values internally
which leads to problems. ConfigParser.ConfigParser will be deprecated in
3.2 in favor of SafeConfigParser. Please use that.
parser'ly yours,
Łukasz Langa
the configparser maintainer for 3.2+
** Affects: configglue
Importance: Undecided
Status: New
--
Use ConfigParser.SafeConfigParser instead of the broken ConfigParser.ConfigParser
https://bugs.launchpad.net/bugs/677108
You received this bug notification because you are a member of
Configglue developers, which is the registrant for configglue.
Status in configglue: New
Bug description:
ConfigParser.ConfigParser is broken in terms of interpolation completeness. It also lets users set() non-string values internally which leads to problems. ConfigParser.ConfigParser will be deprecated in 3.2 in favor of SafeConfigParser. Please use that.
parser'ly yours,
Łukasz Langa
the configparser maintainer for 3.2+
Follow ups
References