On 17 March 2003, David Ascher said:
> Would anyone else like it if the mechanism used for configuring a Quixote
> file could be used both for Quixote itself and for application-specific
> details?

I'm a bit leery of foisting a universal configuration mechanism onto the
world.  (I know, I know, that's kind of rich coming from someone with my
record for trying to foist universal mechanisms for this and that
[cf. distutils, optik] onto the world, but there ya go.)

> Put differently, how are people dealing with configuration files for their
> applications?

For SPLAT! (a still-unreleased bug tracker written as an example Quixote
app), I subclassed Quixote's Config class and use one config file for
all config info, whether it's plain Quixote or specific to SPLAT!.
Things are even more fun with SPLAT!, because there are a couple of
command-line tools, and I wanted to integrate command-line options into
the mix.  The experiment was not a complete success; it's a bit awkward
and fragile.  But I'll attach SPLAT!'s config.py, the default
splat.conf, and one of the command-line tools for your edification and
amusement.  Take with a grain of salt; there's way, way more than one
way to do it.

        Greg

PS. note that I haven't touched SPLAT! in ages, so it refers to some
long-obsolete Quixote config variables.

--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org