RetroSearch Browse

Mon Jan 30 20:20:18 CET 2006 · http://mail.python.org/pipermail/python-dev/2006-January/060224.html

On 1/30/06, Ian Bicking <ianb at colorstudy.com> wrote:
> I don't think enhancing ConfigParser significantly is a good way
> forward.  Because of ConfigParser's problems people have made all sorts
> of workarounds, and so I don't think there's any public interface that
> we can maintain while changing the internals without breaking lots of
> code.  In practice, everything is a public interface.  So I think the
> implementation as it stands should stay in place, and if anything it
> should be deprecated instead of being enhanced in-place.

Somehow that's not my experience. What's so bad about ConfigParser?
What would break if we rewrote the save functionality to produce a
predictable order?

--
--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2006-January/060224.html below:

[Python-Dev] Extension to ConfigParser