[X] The "Vixta.org-098.01.En.iso" file could not be found or is not available. Please select another file.

A python module for ultra simple handling of configuration files. Also useful for human readable data persistence. Flexible and simple.


http://www.voidspace.org.uk/python/configobj.html





Separate each tag with a space.

Release Date:

2009-04-17

Topic:

Operating System:

License:

Intended Audience:

Programming Language:

Registered:

2004-11-03

Ratings and Reviews

Be the first to post a text review of ConfigObj. Rate and review a project by clicking thumbs up or thumbs down in the right column.

Project Feed

  • Tracker artifact added

    posted by mahsofo 25 days ago

  • Tracker artifact added

    sblyth created the programmatic key commenting artifact

    posted by sblyth 193 days ago

  • configobj 4.6.0 file released: configobj-4.6.0.zip

    * Pickling of ConfigObj instances now supported (thanks to Christian Heimes) * 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 section that was supplied as a value (or vice-versa) in the actual config file would cause an exception during validation (the config file is still broken of course, but it is now handled gracefully) * Added ``as_list`` method * Removed the deprecated ``istrue``, ``encode`` and ``decode`` methods * Running test_configobj.py now also runs the doctests in the configobj module * Through the use of validate 1.0.0 ConfigObj can now validate multi-line values 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. 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.

    posted 262 days ago

  • File released: /configobj/4.6.0/configobj-4.6.0.zip

    posted 262 days ago

  • Tracker artifact added

    posted by crenix 306 days ago

  • Tracker comment added

    Anonymous commented on the Setup Updates artifact

    posted by nobody 357 days ago

  • Tracker artifact added

    stevemilner created the Setup Updates artifact

    posted by stevemilner 366 days ago

  • Tracker artifact added

    mgorven created the Interpolate list values artifact

    posted by mgorven 375 days ago

  • Tracker artifact added

    Anonymous created the ' = ' != '=' in configObj.py artifact

    posted by nobody 460 days ago

  • Tracker artifact added

    vila-sf created the python-2.6 compatibility artifact

    posted by vila-sf 465 days ago

Rate and Review

Be the first person to add a text review.

Would you recommend this project?






<

Related Projects

ConfigObj Actions

Thanks for your rating!

Would you also like to write a review?





Skip Review

Thanks for your review!

Get credit for your review by logging in via OpenID. Click your account provider:

No Thanks