Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"include" should take precedence over "is stdlib" #138

Closed
nedbat opened this issue Jul 1, 2011 · 1 comment
Closed

"include" should take precedence over "is stdlib" #138

nedbat opened this issue Jul 1, 2011 · 1 comment
Labels
bug Something isn't working run

Comments

@nedbat
Copy link
Owner

nedbat commented Jul 1, 2011

Dave McLain reported this in irc:

If he explicitly specifies a source file with include= in the coverage constructor, and that file is in the python lib installation directory, then it isn't covered, because the "is stdlib" check kicks in before the "is included" check.

If the user specifies a file to measure, it should be measured, no matter what.


@nedbat
Copy link
Owner Author

nedbat commented Aug 4, 2011

Fixed in <<changeset 935338c27357 (bb)>>.

@nedbat nedbat closed this as completed Aug 4, 2011
@nedbat nedbat added major bug Something isn't working run labels Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working run
Projects
None yet
Development

No branches or pull requests

1 participant