Message218816
| Author |
Trip.Volpe |
| Recipients |
Trip.Volpe, ajaksu2, amaury.forgeotdarc, barry, belopolsky, eric.araujo, eric.snow, nedbat, rhettinger, terry.reedy, tshepang |
| Date |
2014年05月19日.20:34:58 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1400531699.38.0.990814440342.issue2506@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I found this issue just the other day while researching why we were getting false gaps in our test coverage reports (using Ned's coverage module, natch!). I agree that this seems like a fairly minor nuisance, but it's a nuisance that anybody who has tests and measures test coverage will run into sooner or later -- and that's *everybody*, right?
I think some kind of fix ought to be discussed. After all, "it should be possible to have accurate coverage results" is a proposition that seems fairly reasonable to me. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年05月19日 20:34:59 | Trip.Volpe | set | recipients:
+ Trip.Volpe, barry, rhettinger, terry.reedy, amaury.forgeotdarc, belopolsky, ajaksu2, nedbat, eric.araujo, tshepang, eric.snow |
| 2014年05月19日 20:34:59 | Trip.Volpe | set | messageid: <1400531699.38.0.990814440342.issue2506@psf.upfronthosting.co.za> |
| 2014年05月19日 20:34:59 | Trip.Volpe | link | issue2506 messages |
| 2014年05月19日 20:34:58 | Trip.Volpe | create |
|