Fix pytest warning about cov#2708
Merged
gvanrossum merged 1 commit intomasterfrom Jan 18, 2017
Merged
Conversation
Without this I get a pytest warning about cov every time I run it. The cov plugin still gets loaded and I can still generate coverage reports, so I assume that the coverage plugin is loaded automatically. Not sure if we should require a more recent pytest version. This is what the warning looked like: ``` ======================= pytest-warning summary ======================== WP1 None Module already imported so can not be re-written: pytest_cov ```
Member
|
I see this warning too. I've always just ignored it. @cpennington Since you added the |
Contributor
|
I think the |
Member
|
OK, confirmed that things still work, so merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Without this I get a pytest warning about cov every time I run it.
The cov plugin still gets loaded and I can still generate coverage
reports, so I assume that the coverage plugin is loaded
automatically. Not sure if we should require a more recent pytest
version.
This is what the warning looked like: