[issue29747] unittest - assertDoesNotRaise

Vinícius Dantas added the comment: As a last argument: It is a matter of coherence/consistency with unittest's API, given that this module does differentiates errors from failures -- ___ Python tracker

[issue29747] unittest - assertDoesNotRaise

Changes by Vinícius Dantas : -- pull_requests: +453 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue29747] unittest - assertDoesNotRaise

R. David Murray added the comment: 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

[issue29747] unittest - assertDoesNotRaise

New submission from Vinícius Dantas: Unittest provides us some assert methods, yet one is missing: the assertDoesNotRaise context. When running tests, tests may end up as failures, successes or errors. It's worth noting that errors and failures are conceptually different, and that's the point