diff options
| author | fuzzyman <devnull@localhost> | 2009-04-13 19:34:42 +0000 |
|---|---|---|
| committer | fuzzyman <devnull@localhost> | 2009-04-13 19:34:42 +0000 |
| commit | a9fa57ba70e122258003a81a7a613576c4f8ac0f (patch) | |
| tree | 8b17cd90daf65847fa5f6db988185807f849ea98 /docs | |
| parent | cb04f6b0966aada6012c6009ce8db1be111b9087 (diff) | |
| download | configobj-git-a9fa57ba70e122258003a81a7a613576c4f8ac0f.tar.gz | |
Adding the 4.6.0 changes so far to the changelog
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/configobj.txt | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/configobj.txt b/docs/configobj.txt index b9147b4..fb1eab8 100644 --- a/docs/configobj.txt +++ b/docs/configobj.txt @@ -2344,8 +2344,24 @@ From version 4 it lists all releases and changes. 2009/04/13 - Version 4.6.0 -------------------------- +* Pickling of ConfigObj instances now supported +* Hashes in confgspecs are now allowed (see note below) * Replaced use of hasattr (which can swallow exceptions) with getattr +* __many__ in configspecs can refer to scalars (ordinary values) as well as sections. +* You can use ___many___ (three underscores!) where you want to use __many__ as well +* You can now have normal sections inside configspec sections that use __many__ +* You can now create an empty ConfigObj with a configspec, programmatically set values and then validate. +* A repeated section that was supplied as a value in the actual config file would cause an exception (it is still an error but is now handled gracefully) +As a consequence of the changes to configspec handling, when you create a ConfigObj instance and provide a configspec, the configspec attribute is only set on the ConfigObj instance - it isn't set on the sections until you validate. You also can't set the configspec attribute to be a dictionary. This wasn't documented but did work previously. + +.. note:: + + In order to fix the problem with hashes in configspecs I had to turn off the parsing of inline comments in configspecs. This will only affect you if you are using ``copy=True`` when validating and expecting inline comments to be copied from the configspec into the ConfigObj instance (all other comments will be copied as usual). + + If you *create* the configspec by passing in a ConfigObj instance (usual way is to pass in a filename or list of lines) then you should pass in ``_inspec=True`` to the constructor to allow hashes in values. This is the magic that switches off inline comment parsing. + + 2008/06/27 - Version 4.5.3 -------------------------- |