Skip to content

Run coverage.py with coverage/fullcoverage/encodings.py #18

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.

Sign up for GitHub

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

Jump to bottom
Open
brettcannon opened this issue Feb 8, 2017 · 2 comments
Open

Run coverage.py with coverage/fullcoverage/encodings.py #18

brettcannon opened this issue Feb 8, 2017 · 2 comments
Labels
CI help wanted

Comments

@brettcannon
Copy link
Member

https://github.com/nedbat/coveragepy/blob/master/coverage/fullcoverage/encodings.py is a hack which makes sure that coverage.py is imported early enough to cover modules that are imported during interpreter startup. Previously it wasn't included with coverage.py, but @nedbat was nice enough to add fullcoverage to coverage.py in nedbat/coveragepy@3962bc4 for its next release. So this issue is to make sure that no one forgets to take advantage of fullcoverage once it's available on PyPI.
@brettcannon brettcannon added the CI label Feb 8, 2017
This was referenced Feb 11, 2017
Open
Closed
@ncoghlan ncoghlan mentioned this issue Mar 3, 2017
Closed
@ncoghlan
Copy link
Contributor

ncoghlan commented Mar 3, 2017

Just noting that this will be one of the pre-requisites for even considering disallowing reductions in code coverage (as per #38)

@nedbat
Copy link
Member

nedbat commented Apr 5, 2017

The fullcoverage file is now packaged, as of coverage.py 4.4b1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CI help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nedbat @brettcannon @ncoghlan