Antoine Pitrou <pit...@free.fr> added the comment: "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. ---------- nosy: +benjamin.peterson, pitrou _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7849> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
