Message309414
Sometimes it's nice to do extra checks on the error raised and captured by self.assertRaises call.
Yes, the same can be achieved using assertRaises as a context manager and then accessing the `exception` attribute in the context manager, but it looks too cumbersome to just get the exception, when it can be simply returned by the assertRaises call.
Note 1: Currently it returns None, so no backward compatibility problem.
Note 2: assertRaises in testtools does this and is very useful |
|
Date |
User |
Action |
Args |
2018-01-03 15:41:56 | facundobatista | set | recipients:
+ facundobatista |
2018-01-03 15:41:56 | facundobatista | set | messageid: <1514994116.04.0.467229070634.issue32487@psf.upfronthosting.co.za> |
2018-01-03 15:41:55 | facundobatista | link | issue32487 messages |
2018-01-03 15:41:55 | facundobatista | create | |
|