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 r.david.murray
Recipients brett.cannon, inducer, r.david.murray
Date 2014-01-05.18:30:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388946651.9.0.144682128487.issue20131@psf.upfronthosting.co.za>
In-reply-to
Content
The easy answer for unittest is to use assertWarns.  For versions where that doesn't exist you could implement the same technique yourself.  Exposing a 'clear everything' function in the warnings module might not be a bad idea, but otherwise for doctest I'd think the catch_warnings context manager would be the correct answer, and that is documented.

Given the above, I guess this issue is a request to expose a "clear everything" function in the warnings module, which I think is a reasonable idea.

(I think it would be nice to add some support stuff to doctest to make things like this easier, but that is a totally separate issue.)
History
Date User Action Args
2014-01-05 18:30:51r.david.murraysetrecipients: + r.david.murray, brett.cannon, inducer
2014-01-05 18:30:51r.david.murraysetmessageid: <1388946651.9.0.144682128487.issue20131@psf.upfronthosting.co.za>
2014-01-05 18:30:51r.david.murraylinkissue20131 messages
2014-01-05 18:30:51r.david.murraycreate