configglue team mailing list archive
-
configglue team
-
Mailing list archive
-
Message #00157
[Bug 677108] Re: Use ConfigParser.SafeConfigParser instead of the broken ConfigParser.ConfigParser
** Changed in: configglue
Status: In Progress => Fix Committed
** Changed in: configglue
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Configglue developers, which is the registrant for configglue.
https://bugs.launchpad.net/bugs/677108
Title:
Use ConfigParser.SafeConfigParser instead of the broken
ConfigParser.ConfigParser
Status in configglue:
Fix Released
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+
To manage notifications about this bug go to:
https://bugs.launchpad.net/configglue/+bug/677108/+subscriptions
References