[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser

[Łukasz Langa]

Łukasz Langa <lukasz at langa.pl> added the comment:

Yes, so the patch part is already solved. The thing that is still open to discussion is whether we should do something like this:

1. Pending-Deprecate naked the ConfigParser class in 3.2.
2. Deprecate it in 3.3.
3. Remove it in 3.4 and rename SafeConfigParser to ConfigParser.

This is controversial but many developers (myself included) don't see the point in running naked ConfigParser because it's basically SafeConfigParser sans its completeness and predictability.

So, please +1 or -1 the deprecation process idea.

+1 from me

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6517>
_______________________________________