Łukasz Langa <luk...@langa.pl> added the comment: This is unfortunately a backwards compatibility concern. Originally it wasn't made so that set() converts to string or accepts only strings and when the developers realized this mistake, it was too late (there were programs using this misfeature). That's one of the reasons SafeConfigParser was created (hence the name).
As I said in my original answer, SafeConfigParser doesn't let you set() anything but a string and this is how it should have been from the start. But we won't break backwards compatibility now, it's far too late for that I'm afraid. Storing non-string data was misused by some programs by using set() and get() (not getboolean() or getint() etc. but bare get()). I'm closing this as Won't Fix. Thanks for your input, it's very much appreciated. ---------- resolution: -> wont fix _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10387> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
