Guido> What's so bad about ConfigParser?
My guess is that people find its limited nesting, well, limiting. Python
containers being the arbitrary nesting little devils that they are, I can
understand the desire to push the envelope.
It's my opinion that ConfigParser should stay pretty much as it is other
than perhaps adding round trip capability. It is pretty good at reading and
writing Windows INI files, which was what it was designed to do. My guess
is there are a fair number of people who wouldn't want to lose that. Mixing
INI file handling with something more powerful seems doomed. If we want
more sophisticated functionality a new module should be written, or one of
the existing shootout candidates on the Wiki should be chosen and perhaps
enhanced. I have a horse in that race (actually, it's more like a pony).
Skip
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
