Message100242
"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. |
|
Date |
User |
Action |
Args |
2010-03-01 03:34:38 | pitrou | set | recipients:
+ pitrou, brett.cannon, benjamin.peterson, ezio.melotti, flox |
2010-03-01 03:34:38 | pitrou | set | messageid: <1267414478.25.0.456310689331.issue7849@psf.upfronthosting.co.za> |
2010-03-01 03:34:36 | pitrou | link | issue7849 messages |
2010-03-01 03:34:36 | pitrou | create | |
|