Message100242
| Author |
pitrou |
| Recipients |
benjamin.peterson, brett.cannon, ezio.melotti, flox, pitrou |
| Date |
2010年03月01日.03:34:36 |
| SpamBayes Score |
2.8826944e-08 |
| Marked as misclassified |
No |
| Message-id |
<1267414478.25.0.456310689331.issue7849@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
"lazy" sounds like a bad name for that parameter. It makes me think of lazy evaluation, not error checking.
There's also the problem that check_py3k_warnings() will check all DeprecationWarnings, not only py3k-specific ones. We need a Py3kDeprecationWarning subclass.
Besides, there doesn't seem to be any point accepting positional arguments in check_py3k_warnings(). If you want a custom filter, just use check_warnings() instead. |
|