[issue23835] configparser does not convert defaults to strings

Change by STINNER Victor : -- pull_requests: -23600 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23835] configparser does not convert defaults to strings

Change by junyixie : -- nosy: +JunyiXie nosy_count: 7.0 -> 8.0 pull_requests: +23600 pull_request: https://github.com/python/cpython/pull/24821 ___ Python tracker ___

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: That's intentional. In ConfigParser objects this exception would be raised for any other section's assignment already. You want RawConfigParser if you want to put (invalid) types as option values. See: >>> cp = ConfigParser() >>> cp['asd'] = {'a': None}

[issue23835] configparser does not convert defaults to strings

Anthony Sottile added the comment: Unclear if this regression (from this patch) is intentional or not: ``` $ python3.6 -c 'import configparser; configparser.ConfigParser(defaults={"a": None})' $ python3.7 -c 'import configparser; configparser.ConfigParser(defaults={"a": None})' Traceback

[issue23835] configparser does not convert defaults to strings

Change by Barry A. Warsaw : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue23835] configparser does not convert defaults to strings

miss-islington added the comment: New changeset f44203d782e397941c17d96e6a1f9dc1df08b3e6 by Miss Islington (bot) in branch '3.7': bpo-33802: Do not interpolate in ConfigParser while reading defaults (GH-7524) https://github.com/python/cpython/commit/f44203d782e397941c17d96e6a1f9dc1df08b3e6

[issue23835] configparser does not convert defaults to strings

Change by miss-islington : -- pull_requests: +7165 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: New changeset 214f18e49feb6a9d6c05aa09a4bb304905e81334 by Łukasz Langa in branch 'master': bpo-33802: Do not interpolate in ConfigParser while reading defaults (GH-7524) https://github.com/python/cpython/commit/214f18e49feb6a9d6c05aa09a4bb304905e81334

[issue23835] configparser does not convert defaults to strings

Change by Łukasz Langa : -- keywords: +patch pull_requests: +7153 stage: -> patch review ___ Python tracker ___ ___

[issue23835] configparser does not convert defaults to strings

STINNER Victor added the comment: It seems like this issue introduced a regression according to Barry: bpo-33802. -- nosy: +vstinner ___ Python tracker ___

[issue23835] configparser does not convert defaults to strings

Barry A. Warsaw added the comment: I think this introduced a regression in 3.7. See bpo-33802 https://bugs.python.org/issue33802 -- keywords: +3.7regression -patch nosy: +barry priority: normal -> deferred blocker resolution: fixed -> stage: resolved -> status: closed -> open

[issue23835] configparser does not convert defaults to strings

Changes by Łukasz Langa : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: New changeset a5fab17fc11433b2418f626dc51e8a3d07b198ca by Łukasz Langa in branch 'master': bpo-23835: Restore legacy defaults= behavior for RawConfigParser (#3191) https://github.com/python/cpython/commit/a5fab17fc11433b2418f626dc51e8a3d07b198ca --

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: 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

[issue23835] configparser does not convert defaults to strings

Changes by Łukasz Langa : -- pull_requests: +3230 ___ Python tracker ___ ___

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: New changeset ea57923e89aa4a1bde1d4fa1de7d6eacff603683 by Łukasz Langa in branch 'master': bpo-23835: [docs] configparser converts defaults to strings (#3176) https://github.com/python/cpython/commit/ea57923e89aa4a1bde1d4fa1de7d6eacff603683 --

[issue23835] configparser does not convert defaults to strings

Changes by Łukasz Langa : -- pull_requests: +3214 ___ Python tracker ___ ___

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: New changeset 44e6ad87340d50f48daf53b6a61138377d0d0d10 by Łukasz Langa (James Tocknell) in branch 'master': bpo-23835: Enforce that configparser defaults are strings (#2558) https://github.com/python/cpython/commit/44e6ad87340d50f48daf53b6a61138377d0d0d10

[issue23835] configparser does not convert defaults to strings

Changes by Łukasz Langa : -- versions: -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: 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. --

[issue23835] configparser does not convert defaults to strings

R. David Murray added the comment: Thanks. OK, so you agree a fix is appropriate. What about the question of backport/backward compatibility? -- ___ Python tracker

[issue23835] configparser does not convert defaults to strings

Łukasz Langa added the comment: Responded on the PR. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue23835] configparser does not convert defaults to strings

R. David Murray added the comment: 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. -- nosy: +r.david.murray versions: +Python 3.6, Python

[issue23835] configparser does not convert defaults to strings

Changes by James Tocknell : -- pull_requests: +2628 ___ Python tracker ___ ___

[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 docstring of the

[issue23835] configparser does not convert defaults to strings

Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +lukasz.langa type: crash - behavior versions: +Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23835 ___

[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 ConfigParser['DEFAULT'] =