➜

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 eric.araujo
Recipients brett.cannon, eric.araujo, fdrake, georg.brandl, lukasz.langa, michael.foord, r.david.murray, rhettinger, till
Date 2010-08-03.11:06:49
SpamBayes Score 0.0021657175
Marked as misclassified No
Message-id <1280833610.78.0.538188611727.issue6517@psf.upfronthosting.co.za>
In-reply-to
Content 
If ConfigParser is not documented first, the name “SafeConfigParser” becomes strange—safe compared to what? These names have an historical motivation and could become clearer if renamed, but I don’t know if python-dev will agree with this deprecation. Renaming a class to an existing name with different behavior can be bad.

FTR, in my head RawConfigParser is the config parser, and SafeConfigParser is another thing that I’ll maybe use one day.
History
Date User Action Args
2010-08-03 11:06:50eric.araujosetrecipients: + eric.araujo, fdrake, brett.cannon, georg.brandl, rhettinger, r.david.murray, michael.foord, till, lukasz.langa
2010-08-03 11:06:50eric.araujosetmessageid: <1280833610.78.0.538188611727.issue6517@psf.upfronthosting.co.za>
2010-08-03 11:06:49eric.araujolinkissue6517 messages
2010-08-03 11:06:49eric.araujocreate