Repository navigation
ConfigParser parsing failures with default_section and ExtendedInterpolation options #71018
Description
| BPO | 26831 |
|---|---|
| Nosy | @ambv |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2016-04-23.08:53:44.069>
created_at = <Date 2016-04-22.22:37:37.961>
labels = ['invalid', 'type-bug', 'library']
title = 'ConfigParser parsing failures with default_section and ExtendedInterpolation options'
updated_at = <Date 2022-02-17.12:22:23.632>
user = 'https://bugs.python.org/frispete'bugs.python.org fields:
activity = <Date 2022-02-17.12:22:23.632>
actor = 'lukasz.langa'
assignee = 'none'
closed = True
closed_date = <Date 2016-04-23.08:53:44.069>
closer = 'SilentGhost'
components = ['Library (Lib)']
creation = <Date 2016-04-22.22:37:37.961>
creator = 'frispete'
dependencies = []
files = ['42573']
hgrepos = []
issue_num = 26831
keywords = []
message_count = 3.0
messages = ['264031', '264059', '413399']
nosy_count = 3.0
nosy_names = ['frispete', 'SilentGhost', 'lukasz.langa']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26831'
versions = ['Python 3.4']
Activity
frispete commentedon Apr 22, 2016
ConfigParser fails in interesting ways, when using default_section and ExtendedInterpolation options. Running the attached script results in:
ConfigParser() with expected result:
global: [('loglevel', 'WARNING'), ('logfile', '-')]
section1: [('key_a', 'value'), ('key_b', 'morevalue')]
section2: [('key_c', 'othervalue'), ('key_d', 'differentvalue')]
ConfigParser(default_section='global') mangles section separation:
section1: [('loglevel', 'WARNING'), ('logfile', '-'), ('key_a', 'value'), ('key_b', 'morevalue')]
section2: [('loglevel', 'WARNING'), ('logfile', '-'), ('key_c', 'othervalue'), ('key_d', 'differentvalue')]
while it is expected to behave identical.
SilentGhost commentedon Apr 23, 2016
I think there is some misunderstanding of what default_section is supposed to do, in fact in provides default values for *other* section, as the documentation says, it doesn't mangle section separation.
In case of ExtendedInterpolation, the interpolation argument needs to be instantiated, i.e. the call should be:
ConfigParser(interpolation=ExtendedInterpolation())
ambv commentedon Feb 17, 2022
Note: the problem here was due to passing
ExtendedInterpolation(the class) instead ofExtendedInterpolation()(the object). This is now fixed through BPO-41086.