On 1/30/06, Ian Bicking <[EMAIL PROTECTED]> 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/) _______________________________________________ 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
