Łukasz Langa added the comment:
As R. David pointed out, this is fixed in Python 3 by emphasizing configparser
is designed to hold strings at all times. Changing this would break lots of
existing code out there. So, sadly, #wontfix.
Thank you for your report though. If you find the documentati
R. David Murray added the comment:
In python3 you will get an error: "TypeError: option values must be strings".
So, this is an infelicity in the configparser API. Or, rather, I presume it is
a design decision (ie: python shouldn't guess what string format you want the
value to have in the f
New submission from Andreas Hilboll:
Not sure if this is by design (or if I'm doing something utterly stupid), but I
often create a ConfigParser object for my application and then pass this around
(or make it global).
So when I do something like
cfg.set("input_filter", "include_filtered",
