[issue27176] Addition of assertNotRaises

Raymond Hettinger added the comment: I concur with David snd Steven, so closing this as rejected. -- nosy: +rhettinger resolution: -> rejected status: open -> closed ___ Python tracker

[issue27176] Addition of assertNotRaises

R. David Murray added the comment: Agreed. I've never used the distinction between errors and failures myself. -- nosy: +r.david.murray ___ Python tracker

[issue27176] Addition of assertNotRaises

Steven D'Aprano added the comment: Yes. What does such an assertion actually mean? Why would I write `self.assertNotRaises(ValueError, spam, arg)` rather than just call `spam(arg)`? The only difference is that assertNotRaises will treat one specific exception as a test failure rather than a

[issue27176] Addition of assertNotRaises

Changes by SilentGhost : -- nosy: +ezio.melotti, michael.foord, rbcollins versions: +Python 3.6 ___ Python tracker ___

[issue27176] Addition of assertNotRaises

New submission from Bar Harel: I thought of implementing an assertNotRaises to solve the issue of using try...except...fail in order to prevent showing the tests as an error and instead show them as a failure. Is there anything I should consider while implementing it? -- components: