This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lukasz.langa
Recipients brett.cannon, eric.araujo, fdrake, georg.brandl, lukasz.langa, michael.foord, r.david.murray, rhettinger, till
Date 2010-08-03.10:59:58
SpamBayes Score 6.133302e-07
Marked as misclassified No
Message-id <>
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
Date User Action Args
2010-08-03 11:00:01lukasz.langasetrecipients: + lukasz.langa, fdrake, brett.cannon, georg.brandl, rhettinger, eric.araujo, r.david.murray, michael.foord, till
2010-08-03 11:00:01lukasz.langasetmessageid: <>
2010-08-03 10:59:59lukasz.langalinkissue6517 messages
2010-08-03 10:59:58lukasz.langacreate