Use ConfigParser.SafeConfigParser instead of the broken ConfigParser.ConfigParser

Bug #677108 reported by Łukasz Langa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
configglue
Fix Released
Undecided
Unassigned

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+

Related branches

Changed in configglue:
status: New → In Progress
Changed in configglue:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.