[issue23835] configparser does not convert defaults to strings

Changes by James Tocknell : -- pull_requests: +2628 ___ Python tracker <http://bugs.python.org/issue23835> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18391] socket.fromfd()'s API is difficult or impossible to use correctly in general

Changes by James Tocknell : -- nosy: +aragilar ___ Python tracker <http://bugs.python.org/issue18391> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23835] configparser does not convert defaults to strings

James Tocknell added the comment: Here's a patch for 2.7 (based of the head of the 2.7 branch), something similar could be done for 3.4 (I wasn't sure what branch I was supposed to base the patch off, since 3.4 is inactive). The string requirement was already noted in the docstr

[issue23835] configparser does not convert defaults to strings

New submission from James Tocknell: ConfigParser(defaults={1:2.4}) and ConfigParser(defaults={"a":5.2}) cause an exception when configparser tries to perform string operations on 1 and 5.2. I didn't see it documented that defaults must only contain strings, and using Config