Michael Foord <mich...@voidspace.org.uk> added the comment: If we merge the functionality in a single class with a new name then I guess that is fine as it will simplify the documentation rather than complexify it (good word hey). We still need to *mention* the old names so that people finding them in old code can find an up to date reference on them.
Here's what I don't understand about Fred's difficulty with replacing ConfigParser with the sane implementation. After we deprecate ConfigParser as it is now we have two choices. * delete the ConfigParser name - breaking *all* code that uses it and has not been updated * point the name at what is currently called SafeConfigParser - causing a slight risk of incompatibility but likely *improving* most code that hasn't been updated I don't see how the first option could *in any way* be preferable to the second. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6517> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
