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 belopolsky
Recipients belopolsky, benjamin.peterson, brandon-rhodes, eric.araujo, ncoghlan, pitrou
Date 2011-03-18.00:30:16
SpamBayes Score 3.0481633e-07
Marked as misclassified No
Message-id <AANLkTikfdQvD3VU0W0PeKCSqo+x7H3xz=mPwhQFrBqoC@mail.gmail.com>
In-reply-to <1300406582.4.0.122505099603.issue11572@psf.upfronthosting.co.za>
Content
On Thu, Mar 17, 2011 at 8:03 PM, Antoine Pitrou <report@bugs.python.org> wrote:
..
> +1 for not having pragma statements in the stdlib, especially when they target a third-party tool few of us know and use.

"#pragma NO COVER" is recognized by stdlib trace module, so it is not
specific to a third-party tool.  I don't like #pragma myself.  This is
very "unpythonic" choice.  I would be much happier if it was simply '#
NO COVER' or something even less conspicuous.  I do believe, however
that some mechanism should be used to prevent trace from highlighting
spurious lines as lacking coverage.

> Beside, while coverage measurements are useful, trusting them that actual coverage is complete is IMO a bit foolish.
> It's not just about running every line of code.

Agree, but running every line of code is a good first step.  For
example, it is *very* useful for identifying lack of coverage for
error conditions.
History
Date User Action Args
2011-03-18 00:30:17belopolskysetrecipients: + belopolsky, ncoghlan, pitrou, benjamin.peterson, eric.araujo, brandon-rhodes
2011-03-18 00:30:16belopolskylinkissue11572 messages
2011-03-18 00:30:16belopolskycreate