This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
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.
Date User Action Args
2014-05-19 20:34:59Trip.Volpesetrecipients: + Trip.Volpe, barry, rhettinger, terry.reedy, amaury.forgeotdarc, belopolsky, ajaksu2, nedbat, eric.araujo, tshepang, eric.snow
2014-05-19 20:34:59Trip.Volpesetmessageid: <>
2014-05-19 20:34:59Trip.Volpelinkissue2506 messages
2014-05-19 20:34:58Trip.Volpecreate