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

Łukasz Langa report at bugs.python.org
Tue Aug 3 17:20:06 CEST 2010


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

There IS one more option that seems to be better than all of the above:

1. Add an interpolation=True argument to RawConfigParser __init__ and move the interpolating functionality from SafeConfigParser to it.
2. Rename RawConfigParser to ConfigParser leaving the old name in PendingDeprecation with interpolation=False.
3. Make an alias for SafeConfigParser pointing to ConfigParser with PendingDeprecation.

We can do all this for 3.2 I guess without inflicting any actual damage. It will fix more bugs in running code that break config files.

Maybe we shouldn't be so afraid after all and just clean it up.

----------

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


More information about the Python-bugs-list mailing list