Message 207372 - Python tracker

➜

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	inducer
Recipients	inducer
Date	2014-01-05.12:39:28
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1388925569.4.0.616104920228.issue20131@psf.upfronthosting.co.za>
In-reply-to

Content
For tests and doctests, it is often desirable to show or verify that a certain warning occurs. Unfortunately, if the warning has been hit previously, it will not be issued again. It would be great if there were a documented, unified way to reset this 'seen' flag. Related stackoverflow posts showing that I'm not the first person to have this need: * https://stackoverflow.com/questions/19428761/python-showing-once-warnings-again-resetting-all-warning-registries * https://stackoverflow.com/questions/2418570/testing-warnings-with-doctest Neither of these has a satisfactory solution.

For tests and doctests, it is often desirable to show or verify that a certain warning occurs. Unfortunately, if the warning has been hit previously, it will not be issued again. It would be great if there were a documented, unified way to reset this 'seen' flag.

Related stackoverflow posts showing that I'm not the first person to have this need:

* https://stackoverflow.com/questions/19428761/python-showing-once-warnings-again-resetting-all-warning-registries
* https://stackoverflow.com/questions/2418570/testing-warnings-with-doctest

Neither of these has a satisfactory solution.

History
Date	User	Action	Args
2014-01-05 12:39:29	inducer	set	recipients: + inducer
2014-01-05 12:39:29	inducer	set	messageid: <1388925569.4.0.616104920228.issue20131@psf.upfronthosting.co.za>
2014-01-05 12:39:29	inducer	link	issue20131 messages
2014-01-05 12:39:28	inducer	create