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, fdrake, georg.brandl, lukasz.langa, r.david.murray, rhettinger, till
Date 2010-07-24.06:38:52
SpamBayes Score 0.006160788
Marked as misclassified No
Message-id <>
> The documentation should promote RawConfigParser, and note
> SafeConfigParser and ConfigParser as remaining for backward
> compatibility for existing software. 

That is another way to go around this. Anyway, ConfigParser is the least predictable of all three for end users and the documentation should be adjusted to emphasize this. 

> Maintainers of legacy software
> using ConfigParser should be encouraged to convert to SafeConfigParser
> (or even RawConfigParser) if possible.

That's another comment that should appear in the documentation.

> Documentation changes should be sufficient; deprecation warnings
> typically generate more pain than good.

Isn't is what I was saying above?
Date User Action Args
2010-07-24 06:38:54lukasz.langasetrecipients: + lukasz.langa, fdrake, brett.cannon, georg.brandl, rhettinger, r.david.murray, till
2010-07-24 06:38:54lukasz.langasetmessageid: <>
2010-07-24 06:38:52lukasz.langalinkissue6517 messages
2010-07-24 06:38:52lukasz.langacreate