Message190399
According to R. David Murray in Python core-mentorship mailing list addressing me:
"It could be that the bug is that the i is not used...it may have been
intended to be used in an extended error message in the asserts, so that
it would be clear which input failed. In any case, I think the best
fix here would probably be to use the new subtests support in unittest."
So I used subTest feature in the second patch I upload according to his advice.
What do you think? subTest can recognize where the test fails immediately as well. You just have to count the line in the loop. |
|
Date |
User |
Action |
Args |
2013-05-31 10:40:51 | vajrasky | set | recipients:
+ vajrasky, pitrou, ezio.melotti, michael.foord, serhiy.storchaka |
2013-05-31 10:40:51 | vajrasky | set | messageid: <1369996851.34.0.356138234706.issue18106@psf.upfronthosting.co.za> |
2013-05-31 10:40:51 | vajrasky | link | issue18106 messages |
2013-05-31 10:40:50 | vajrasky | create | |
|