Message188390
| Author |
brett.cannon |
| Recipients |
benjamin.peterson, brett.cannon, eric.araujo, ezio.melotti, r.david.murray, vstinner |
| Date |
2013年05月04日.18:38:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1367692713.21.0.483447162921.issue17177@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
While thinking about asking on G+ for feedback, I realized that if I get this to the point of a module-level warning, it won't be a big deal. It would be just like warnings you deal with when supporting old versions of Python along with newer versions where things are now deprecated. That way users of imp could just do::
with warnings.catch_warnings():
warnings.simplefilter("ignore")
import imp
and be done with it. This means still striving to deprecate every function in imp so that it can all be replaced with a single module-level deprecation is a reasonable goal to have. |
|