[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna report at bugs.python.org
Wed Mar 17 15:06:07 CET 2010


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

I hesitate to do it differently:

with check_warnings(('', RuntimeWarning)):
 ==> translate to check_warnings(('', RuntimeWarning), quiet=False)

with check_warnings():
 ==> translate to check_warnings(quiet=True)

If the developer passes some arguments to the function, it means that he expects some warnings, and he should not need to add "quiet=False" each time.
And it preserves backward compatibility for existing code.

I guess that we push same behavior for 3.x.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8155>
_______________________________________


More information about the Python-bugs-list mailing list