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, eric.araujo, fdrake, georg.brandl, lukasz.langa, michael.foord, r.david.murray, rhettinger, till
Date 2010-08-03.13:10:23
SpamBayes Score 0.0054367487
Marked as misclassified No
Message-id <>
In-reply-to <>
Making ConfigParser an alias for SafeConfigParser creates a silent
behavioral change.  An application developer may not realize that
users rely on the "full" ConfigParser anti-glory and end up breaking
their configurations without so much as providing a heads-up in the
application news.


So long as the application developer has to change their code to move
away from ConfigParser, there's a better chance of affected end users
receiving a heads-up.
Date User Action Args
2010-08-03 13:10:25fdrakesetrecipients: + fdrake, brett.cannon, georg.brandl, rhettinger, eric.araujo, r.david.murray, michael.foord, till, lukasz.langa
2010-08-03 13:10:23fdrakelinkissue6517 messages
2010-08-03 13:10:23fdrakecreate