Message111620
| Author |
michael.foord |
| Recipients |
brett.cannon, fdrake, georg.brandl, lukasz.langa, michael.foord, r.david.murray, rhettinger, till |
| Date |
2010年07月26日.14:17:05 |
| SpamBayes Score |
0.0038466458 |
| Marked as misclassified |
No |
| Message-id |
<1280153826.9.0.677023354104.issue6517@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
It is (very) unfortunate that configparser.ConfigParser should *not* be used and that configparser.SafeConfigParser is the correct class instead.
I would be *in favour* of deprecating ConfigParser and eventually renaming SafeConfigParser back to ConfigParser (leaving SafeConfigParser as an alias).
Now that deprecation warnings are silent by default this should be less of an issue. |
|