← Back to team overview

configglue team mailing list archive

[Bug 677108] Re: Use ConfigParser.SafeConfigParser instead of the broken ConfigParser.ConfigParser

 

** Changed in: configglue
       Status: New => In Progress

-- 
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:
  In Progress

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+



References