-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Coveralls uses internal undocumented parts of coverage.py #47
Comments
I guess it's not too hard to make coveralls work with coverage 4.0b. However, adding newline to the end of python source file changes results a bit, compared to previous coverage version. Why is newline necessary? |
Thanks for looking into updating the support. 4.0 is not in beta yet, so the interfaces still are not finished, so it may be early to write code. The newline is only necessary in some places (compiling to bytecode), and I could adjust how it is done, but can you tell me what kind of result changes you are seeing? I don't worry if the result numbers shift up or down a little bit. |
I'm using a custom reporter to get both coverage data and source file at the same time.
As coverage.py adds an empty newline to the end of the file, I'm seeing this extra line in sources and in coverage output. It's a minor discrepancy, but still... Example: running coverage example/runtests.py results (full pytest output) Coverage 3.X:
Coverage 4.0a2:
I don't think that adding one extra newline changes coverage numbers much, just wanted to let you know. |
Thanks for the explanation. |
Closing this in favor of #81 |
I'm heavily refactoring coverage.py for version 4.0. I tried to release an alpha, but it broke coveralls, and therefore many people's tests on Travis:
We should work together on how to fix it.
The text was updated successfully, but these errors were encountered: