[Configobj-develop] Configuring Turbogears

[<fuz...@vo...>]

{emo;newspaper} `Turbogears <http://www.turbogears.com/>`_ is arguably the *hottest* [#]_ Python project there is right now.

Apparently they're having problems with their current configuration system and Python 2.3. They are/were using pseudo-python files for configuration. Yesterday I discovered this message, from Kevin Dangoor, on the Turbogears Mailing List :

    `Config File Verdict <http://groups.google.co.uk/group/turbogears/browse_frm/thread/f77979ad0e1dacd0/b97cc6d6af9439d6?tvc=1&q=turbogears+configobj#b97cc6d6af9439d6>`_

    | *So, taking into account the various bits of input and the fact that* 
    | *there would appear to be a problem with the new style configs and*
    | *Python 2.3, I'm going to change our config system over to using*
    | **ConfigObj**. 

Blimey. {sm;:-)}

I don't think it's set in stone yet, but if Turbogears switch to using `ConfigObj <http://www.voidspace.org.uk/python/configobj.html>`_ that will be fantastic news.

In the same thread, Mike Orr responds with the following comments on **ConfigObj** :

    | *It looks pretty complete.  I like the validator, conversion to ints*
    | *and lists, triple-quoted strings, and keeping the keys/values in* 
    | *order.  I suppose I should like the multi-level sections. The* 
    | *comma-separated list feature is cool, and I guess it has enough* 
    | *safeguards to distinguish lists from strings.* 

I'm not sure what he means by *should like*, but it's nice to see ConfigObj's features appreciated. {sm;:-p}

.. [#] Well, along with `Django <http://www.djangoproject.com/>`_, `BitTorrent <http://www.bittorrent.com/>`_ and a few others.