You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug in ConfigParser when setting new values in extended interpolation #70656
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=Noneclosed_at=<Date2016-03-02.09:53:47.923>created_at=<Date2016-03-02.09:40:40.534>labels= ['invalid', 'library', 'type-crash']
title='Bug in ConfigParser when setting new values in extended interpolation'updated_at=<Date2022-02-17.12:22:51.625>user='https://bugs.python.org/MichaelJacob'
Note: the problem here was due to passing ExtendedInterpolation (the class) instead of ExtendedInterpolation() (the object). This is now fixed through BPO-41086.
Activity
MichaelJacob commentedon Mar 2, 2016
There seems to be a bug in configparser when setting new values in extended interpolation:
python --version
Python 3.5.1
It works ithout extended interpolation, though.
MichaelJacob commentedon Mar 2, 2016
My bad.
ConfigParser expects an interpolation object, not a class.
Instead of c=ConfigParser(interpolation=ExtendedInterpolation)
you need to create it with:
Sorry about that.
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.