i dont know about your experience with config files, but there
thousands of formats. on the python side -- just in this conversation,
we mentioned ConfigObj, ConfigParser and the Config module i linked to.
when everybody writes his own config, you get loads of unique formats.
anyway, for all the c
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 persisten
and just as i was writing, this was added to lang.python.announce:
http://groups.google.com/group/comp.lang.python.announce/browse_thread/thread/7a6cbcd8070627a0/24a7b35599f65794#24a7b35599f65794
-tomer
--
http://mail.python.org/mailman/listinfo/python-list
hey
i've been seeing lots of config-file-readers for python. be it
ConfigObj (http://www.voidspace.org.uk/python/configobj.html) or the
like. seems like a trend to me.
i came to this conclusion a long time ago: YOU DON'T NEED CONFIG FILES
FOR PYTHON. why re-invent stuff and parse text by yourself,
__add__ is called for the + operator
__iadd__ is called for the += operator
if __iadd__ doesnt exist, fallbacks to __add__
you know what they say for such things: rtfm.
--
http://mail.python.org/mailman/listinfo/python-list
