Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!news2.arglkargh.de!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Neil Cerutti Newsgroups: comp.lang.python Subject: Re: Standard config file format Date: 6 Apr 2011 12:46:43 GMT Organization: Norwich University Lines: 18 Message-ID: <9035ljFq2oU5@mid.individual.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: individual.net WZ8Obj8tEjSzztoi9TZdFAW610XMyF/Lrg5Jwe/TYGOwrjMuFE Cancel-Lock: sha1:E5y9nd1i4R0kOve8foN4PB7YiQI= User-Agent: slrn/0.9.9p1/mm/ao (Win32) Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:2702 On 2011-04-06, Chris Rebert wrote: > On Tue, Apr 5, 2011 at 7:16 PM, Vincent Davis > wrote: >> I am working on a program to monitor directory file changes >> and am would like a configuration file. This file would >> specify email addresses, file and directory locations...... Is >> there a preferred format to use with python? > > ConfigParser supports an INI-like format: > http://docs.python.org/library/configparser.html A bonus for users of Python 3.2 is that ConfigParser now detects multiply defined sections. I installed 3.2 yesterday and thus discovered a bug in a large config file that's been there for seven years. -- Neil Cerutti