[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

[Brett Cannon]

Brett Cannon <brett at python.org> added the comment:

On Sat, Sep 6, 2008 at 11:31 AM, Barry A. Warsaw <report at bugs.python.org> wrote:
>
> Barry A. Warsaw <barry at python.org> added the comment:
>
> Sounds good.  This needs to go into 2.6 and 3.0.

Oh, definitely.

>  And while you're add
> it, can you add catch_warnings to the __all__?
>

Yep. And I will also change the __init__() so that it properly forces
keyword-only arguments in 2.6 like 3.0.

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