[EMAIL PROTECTED] wrote: > if you are really so scared of letting others exploit your config > scripts, then use the second, pickled fashion. that way you can store > the file at $HOME/blah-config.pkl, and everybody's happy. > > still, my point is we dont need special config mechanisms, since the > builtin ones, like object persistency (sp) or python scripts are good > enough, less buggy, and dont require you to learn thousands of config > formats. >
Well... ConfigObj uses the same format as ConfigParser, which the basic ini style. The message is that config files are for users, and so should be in a format convenient for them - not for the machine. Call your users cry-babies if yu want, you won't have many... > and you can even edit pickled files by hand (protocol 0 i believe). > it's not that complicated. > If you're happy with a hardwired config file, you don't need a config file at all. Fuzzyman http://www.voidspace.org.uk/python/index.shtml > > -tomer -- http://mail.python.org/mailman/listinfo/python-list