Message243567
| Author |
serhiy.storchaka |
| Recipients |
Claudiu.Popa, berker.peksag, daniel.wagner-hall, ezio.melotti, martin.panter, michael.foord, r.david.murray, serhiy.storchaka |
| Date |
2015年05月19日.09:14:26 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1432026868.6.0.475324314482.issue15836@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Core developers left a couple of notes and the patch itself is outdated. Here is updated patch that addresses all comments. It also extends the checking to assertRaisesRegex(), assertWarns() and assertWarnsRegex().
There is a risk to break existing incorrect tests if the argument is a tuple. They can be passed for now because caught exception or warning is found before incorrect value. For example:
with self.assertRaises((ValueError, None)):
int('a') |
|