This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lukasz.langa
Recipients Michael.Müller, lukasz.langa, r.david.murray
Date 2014-03-17.01:15:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395018949.97.0.463472812025.issue20943@psf.upfronthosting.co.za>
In-reply-to
Content
Michael, what you wish is already a part of configparser. Let's use this as an example:

>>> p = configparser.ConfigParser()
>>> p.read_string("""
... [one]
... opt=val
... [two]
... num=1
... str=bzz
... bool=true
... """)

When asking for a specific section, you get a SectionProxy object. It has a dict-like API but is not a dict:

>>> p['two']
<Section: two>
>>> isinstance(p['two'], dict)
False

The reason for that is two-fold: firstly this enables us to make changes made on a section object persistent within the main parser. Secondly, this enables us to add configparsser-specific functionality (like dynamic interpolation, type conversions, etc.):

>>> p['two']['num']
'1'
>>> p['two'].getint('num')
1
>>> p['two']['str'] = 'bool is %(bool)s'
>>> p['two']['str']
'bool is true'
>>> p['two']['bool'] = 'false'
>>> p['two']['str']
'bool is false'

Because the section proxy object follows the dict API very closely, it's trivial to convert a section to a dict:

>>> dict(p['two'])
{'str': 'bool is false', 'bool': 'false', 'num': '1'}

Note, however, that this sets in stone interpolations and doesn't provide built-in type conversions.
History
Date User Action Args
2014-03-17 01:15:52lukasz.langasetrecipients: + lukasz.langa, r.david.murray, Michael.Müller
2014-03-17 01:15:49lukasz.langasetmessageid: <1395018949.97.0.463472812025.issue20943@psf.upfronthosting.co.za>
2014-03-17 01:15:49lukasz.langalinkissue20943 messages
2014-03-17 01:15:44lukasz.langacreate