why use special config formats?
sybrenUSE at YOURthirdtower.com.imagination
Fri Mar 10 17:31:57 CET 2006
tomerfiliba at gmail.com enlightened us with:
> 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.
Ehm... and how is a user supposed to edit that? I wouldn't be 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.
Oh, and the ConfigParser module requires you to learn *thousands* of
config formats. Right.
I think you need to get real.
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
More information about the Python-list