Message112598
| 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 |
<AANLkTi=CXoMbR7dAVGhXqpeTzjjy-LDjeEpOdTvXmp3h@mail.gmail.com> |
| In-reply-to |
<1280840267.35.0.868080546941.issue6517@psf.upfronthosting.co.za> |
| Content |
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.
-1
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. |
|