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 fdrake
Recipients brett.cannon, fdrake, georg.brandl, lukasz.langa, r.david.murray, rhettinger, till
Date 2010-07-24.04:24:28
SpamBayes Score 0.019040491
Marked as misclassified No
Message-id <AANLkTi=QaCi=WX5VcVXJYfyh=QC3JW7hHewhtx3ToMtO@mail.gmail.com>
In-reply-to <1279935812.4.0.0588481169309.issue6517@psf.upfronthosting.co.za>
Content
I disagree.

The documentation should promote RawConfigParser, and note
SafeConfigParser and ConfigParser as remaining for backward
compatibility for existing software.  Maintainers of legacy software
using ConfigParser should be encouraged to convert to SafeConfigParser
(or even RawConfigParser) if possible.

Documentation changes should be sufficient; deprecation warnings
typically generate more pain than good.
History
Date User Action Args
2010-07-24 04:24:29fdrakesetrecipients: + fdrake, brett.cannon, georg.brandl, rhettinger, r.david.murray, till, lukasz.langa
2010-07-24 04:24:28fdrakelinkissue6517 messages
2010-07-24 04:24:28fdrakecreate