[issue8880] ConfigParser.set does not convert non-string values

Edwin Pozharski added the comment: Thanks - gotta rtfm :) On Wed, Jun 2, 2010 at 5:33 PM, R. David Murray wrote: > > R. David Murray added the comment: > > Use SafeConfigParser instead, then you can't make the mistake of passing > non-strings to set. > > We really should update the docs so th

[issue8880] ConfigParser.set does not convert non-string values

Éric Araujo added the comment: See # -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8880] ConfigParser.set does not convert non-string values

R. David Murray added the comment: Use SafeConfigParser instead, then you can't make the mistake of passing non-strings to set. We really should update the docs so that ConfigParser is doced only in a 'deprecated' section. But that's a different issue. (Care to open it, merwok? :) ---

[issue8880] ConfigParser.set does not convert non-string values

Éric Araujo added the comment: Would that mean that booleans would be converted to strings on set and converted back on get? Seems wasteful. (I’ve changed the version field for this bug. Its meaning is not “versions this applies to” but “versions that will get a fix”, and 3.2 is the only acti

[issue8880] ConfigParser.set does not convert non-string values

New submission from Edwin Pozharski : set() method of ConfigParser accepts boolean True/False as values at runtime without converting them to strings internally. As a result, getboolean() method reports the following error File "/usr/lib/python2.6/ConfigParser.py", line 350, in getboolean