Łukasz Langa <luk...@langa.pl> added the comment: Eric, while I agree that would be nice as well, renaming each and every parser in the module will be more problematic for sure.
*** TO ALL: WHAT DO YOU SAY TO A PATH LIKE THIS *** 1) In 3.2 we add an alias: InterpolatingConfigParser = SafeConfigParser 1.1) In 3.2 we Pending-Deprecate: ConfigParser (message about it being removed in 3.4) SafeConfigParser (message about it being renamed to InterpolatingConfigParser in 3.4, a name you can already use) 2) In 3.3 we Deprecate: ConfigParser SafeConfigParser Same messages. 3) In 3.4 we remove ConfigParser and rename SafeConfigParser to InterpolatingConfigParser (removing the alias). So then we have two to choose from: Raw and Interpolating. As you see there's no default ConfigParser any more. I like that because it opens a new possibility which I would wait with until 3.5: re-introduce ConfigParser but as a completely new subclass that has better but backwards incompatible defaults. For now most of the new functionality I've added is turned off by default because of backwards compatibility reasons and this is unfortunate. ---------- _______________________________________ 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
