This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry, benjamin.peterson, brett.cannon, exarkun, ncoghlan, pitrou
Date 2008-09-09.12:20:44
SpamBayes Score 0.00032456924
Marked as misclassified No
Message-id <1220962844.97.0.865609986432.issue3781@psf.upfronthosting.co.za>
In-reply-to
Content
With a name like catch_warnings() in the warnings module, it will
definitely get used in production code to suppress warnings.  If its
intended to be used only by tests, then it belongs somewhere else.  If
not test_support then maybe unittest.  If it were moved then I wouldn't
care about the bug that all other warnings caught are inaccessible.

You'd still have to fix the w.messages attribute to be None if there
were no warnings raised.
History
Date User Action Args
2008-09-09 12:20:45barrysetrecipients: + barry, brett.cannon, exarkun, ncoghlan, pitrou, benjamin.peterson
2008-09-09 12:20:44barrysetmessageid: <1220962844.97.0.865609986432.issue3781@psf.upfronthosting.co.za>
2008-09-09 12:20:44barrylinkissue3781 messages
2008-09-09 12:20:44barrycreate