Message112618
| Author |
michael.foord |
| Recipients |
brett.cannon, eric.araujo, fdrake, georg.brandl, lukasz.langa, michael.foord, r.david.murray, rhettinger, till |
| Date |
2010年08月03日.15:11:07 |
| SpamBayes Score |
3.7795016e-05 |
| Marked as misclassified |
No |
| Message-id |
<1280848269.7.0.0226647102449.issue6517@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Getting *rid* of the name ConfigParser would be annoying and cause *gratuitous* code breakage.
If we are going to keep the name but get rid of the "unsafe" version then we can only replace it with what is now SafeConfigParser - as it is almost entirely compatible with it. (Modulo the bug fixing "behavioural change".)
So the real choices are:
* leave ConfigParser as it is
* deprecate it but not remove it (so as not to needlessly break code)
* deprecate now and replace with SafeConfigParser later
Only the last of these is a positive step forwards... :-)
(Strongly -1 on introducing *yet another name* to refer to these classes by.) |
|