Title: configparser does not convert defaults to strings
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: aragilar, lukasz.langa, r.david.murray
Priority: normal Keywords: patch

Created on 2015-04-01 04:23 by aragilar, last changed 2017-08-27 22:05 by lukasz.langa. This issue is now closed.

File name Uploaded Description Edit
py27-config-fix.patch aragilar, 2015-04-08 05:26 review
Pull Requests
URL Status Linked Edit
PR 2558 merged aragilar, 2017-07-04 06:10
PR 3176 merged lukasz.langa, 2017-08-21 23:16
PR 3191 merged lukasz.langa, 2017-08-22 19:01
Messages (10)
msg239768 - (view) Author: James Tocknell (aragilar) * Date: 2015-04-01 04:23
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 ConfigParser['DEFAULT'] = {1:2.4} does the necessary string conversion, so it looks like there should be some conversion done to the defaults.
msg240249 - (view) Author: James Tocknell (aragilar) * Date: 2015-04-08 05:26
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 docstring of the configparser module, but that's not mentioned in the main docs. Also, I wasn't sure where to put a test in because there was not located in Lib/test.
msg297793 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2017-07-06 03:41
I'm guessing we can only do something here in 3.7, for backward compatibility reasons, but maybe I'm wrong.  Hopefully Lukasz will notice the activity on the issue and have time to take a look.
msg298205 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2017-07-12 12:16
Responded on the PR.
msg298234 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2017-07-12 16:50
Thanks.  OK, so you agree a fix is appropriate.  What about the question of backport/backward compatibility?
msg298279 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2017-07-13 10:21
Backwards compatibility will be considered when the patch is ready. I'm not overly worried about fixing a case that currently raises exceptions all over the place. There's few compatibility concerns that we need to consider in this case.
msg300660 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2017-08-21 22:46
New changeset 44e6ad87340d50f48daf53b6a61138377d0d0d10 by Łukasz Langa (James Tocknell) in branch 'master':
bpo-23835: Enforce that configparser defaults are strings (#2558)
msg300661 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2017-08-21 23:23
New changeset ea57923e89aa4a1bde1d4fa1de7d6eacff603683 by Łukasz Langa in branch 'master':
bpo-23835: [docs] configparser converts defaults to strings (#3176)
msg300717 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2017-08-22 19:06
I merged the original fix and documented it. I thought about it some more and remembered that RawConfigParser objects do in fact support non-string values by historical coincidence. It's unfortunately a popular idiom with old programs to load some configuration defaults using the `defaults=` keyword and later use the legacy get() and set() API which doesn't check types inside. A config file like this cannot be safely written back to a file, etc.

I would very much like to get rid of RawConfigParser entirely but we're stuck with it due to backwards compatibility. So, to fix the regression, I created PR 3191.
msg300791 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2017-08-24 16:43
New changeset a5fab17fc11433b2418f626dc51e8a3d07b198ca by Łukasz Langa in branch 'master':
bpo-23835: Restore legacy defaults= behavior for RawConfigParser (#3191)
Date User Action Args
2017-08-27 22:05:43lukasz.langasetstatus: open -> closed
resolution: fixed
stage: resolved
2017-08-24 16:43:58lukasz.langasetmessages: + msg300791
2017-08-22 19:06:09lukasz.langasetmessages: + msg300717
2017-08-22 19:01:59lukasz.langasetpull_requests: + pull_request3230
2017-08-21 23:23:40lukasz.langasetmessages: + msg300661
2017-08-21 23:16:06lukasz.langasetpull_requests: + pull_request3214
2017-08-21 22:46:35lukasz.langasetmessages: + msg300660
2017-08-21 21:18:44lukasz.langasetversions: - Python 2.7, Python 3.5, Python 3.6
2017-07-13 10:21:36lukasz.langasetmessages: + msg298279
2017-07-12 16:50:50r.david.murraysetmessages: + msg298234
2017-07-12 12:16:12lukasz.langasetmessages: + msg298205
2017-07-06 03:41:26r.david.murraysetnosy: + r.david.murray

messages: + msg297793
versions: + Python 3.6, Python 3.7, - Python 3.4
2017-07-04 06:10:32aragilarsetpull_requests: + pull_request2628
2015-04-08 05:26:55aragilarsetfiles: + py27-config-fix.patch
keywords: + patch
messages: + msg240249
2015-04-01 06:59:56serhiy.storchakasetnosy: + lukasz.langa

type: crash -> behavior
versions: + Python 3.5
2015-04-01 04:23:08aragilarcreate