[issue26831] ConfigParser parsing failures with default_section and ExtendedInterpolation options

2022-02-17 Thread Łukasz Langa
Łukasz Langa added the comment: Note: the problem here was due to passing `ExtendedInterpolation` (the class) instead of `ExtendedInterpolation()` (the object). This is now fixed through BPO-41086. -- ___ Python tracker

[issue26831] ConfigParser parsing failures with default_section and ExtendedInterpolation options

2016-04-23 Thread SilentGhost
SilentGhost added the comment: 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

[issue26831] ConfigParser parsing failures with default_section and ExtendedInterpolation options

2016-04-22 Thread Hans-Peter Jansen
New submission from Hans-Peter Jansen: 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',