[ANN] ConfigObj 4.3.2 Released

[Fuzzyman]

`ConfigObj 4.3.2 <http://www.voidspace.org.uk/python/configobj.html>`_
has just been released.

You can download it from `configobj-4.3.2.zip
<http://www.voidspace.org.uk/cgi-bin/voidspace/downman.py?file=configobj-4.3.2.zip>`_.

ConfigObj is a config file reader and writer. It has *many* features,
but the main one is that it is simple to use. Its features include :

* Nested sections (subsections), to any level
* List values
* Multiple line values
* String interpolation (substitution)
* Integrated with a powerful validation system

    - including automatic type checking/conversion
    - repeated sections
    - and allowing default values

* All comments in the file are preserved
* The order of keys/sections is preserved
* No external dependencies
* Full Unicode support
* A powerful ``unrepr`` mode for storing basic datatypes

This is a bugfix and minor feature enhancement release. There is a
bugfix in `unrepr mode
<http://www.voidspace.org.uk/python/configobj.html#unrepr-mode>`_, and
exception handling has been improved.

The full changelog is :

    Changed error handling, if parsing finds a single error then that
error will be re-raised. That error will still have an ``errors`` and a
``config`` attribute. That means the error will be more comprehensible.

    Fixed bug where '\n' terminated files could be truncated.

    Bugfix in ``unrepr`` mode, it couldn't handle '#' in values.
(Thanks to Philippe Normand for the report.)

    As a consequence of this fix, ConfigObj doesn't now keep inline
comments in ``unrepr`` mode. This is because the parser in the
`compiler package <http://docs.python.org/lib/compiler.html>`_ doesn't
keep comments. {sm;:-)}

    Error messages are now more useful. They tell you the number of
parsing errors and the line number of the first error. (In the case of
multiple errors.)

    Line numbers in exceptions now start at 1, not 0.

    Errors in ``unrepr`` mode are now handled the same way as in the
normal mode. The errors stored will be an ``UnreprError``.

There is also a proposal to support `PEP 292
<http://www.python.org/dev/peps/pep-0292/>`_ string substitution (which
is much better). This will be the target of the next release of
**ConfigObj**.