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 r.david.murray, viniciusd
Date 2017-03-07.14:13:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488895994.19.0.0956321241936.issue29747@psf.upfronthosting.co.za>
In-reply-to
Content
This has already been discussed and rejected (issue 14403).  In practice the distinction between a failure and an error is not useful, and a comment in the test is IMO clearer than a no-op context manager: you can use a positive sentence instead of the reader having to understand a double negative ("Make sure there is an alert present; this will raise if not.")

The fact that there is no method to check that there is an alert sounds like a missing feature somewhere outside of Python?

Finally, if having this would in your group's opinion make your test code better, you can add it to your own TestCase subclass.  But our conclusion was that it doesn't belong in the stdlib.
History
Date User Action Args
2017-03-07 14:13:14r.david.murraysetrecipients: + r.david.murray, viniciusd
2017-03-07 14:13:14r.david.murraysetmessageid: <1488895994.19.0.0956321241936.issue29747@psf.upfronthosting.co.za>
2017-03-07 14:13:14r.david.murraylinkissue29747 messages
2017-03-07 14:13:13r.david.murraycreate