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?
to your account
Originally reported by schlauch (Bitbucket: schlauch, GitHub: schlauch)
Since 3.6 the package name is missing. I think the problem is the optimization of the package name. See xmlreport.py line 95 (xml_file):
In 3.5 os.path.split has been used... However, this has been removed by commit:
The text was updated successfully, but these errors were encountered:
Can you provide a test case that demonstrates the regression?
Sorry, something went wrong.
Original comment by schlauch (Bitbucket: schlauch, GitHub: schlauch)
I attached a small project which illustrates the problem. It also contains the coverage XML reports which I created with version 3.5.3 and 3.6.:
The problem is the name attribute in the package tag.
For more information see the README.txt.
Original comment by Camilo Nova (Bitbucket: camilonova, GitHub: camilonova)
Also happens to me as well for versions 3.6 and 3.7
Original comment by Lex Berezhny (Bitbucket: eukreign, GitHub: eukreign)
@camilonova try my pull request #28 it resolves this issue and also adds support for defining package depth
Original comment by Matt Wright (Bitbucket: mattupstate, GitHub: mattupstate)
I just downgraded from 3.7.1 to 3.5.0. With 3.7.1, package name was missing. With 3.5.0, package name was _not_missing.
@nedbat Can you take a look again at this issue? seems https://bitbucket.org/ned/coveragepy/pull-request/28/package-depth-for-xml-report fixes it.
@nedbat the pull request was updated so it can be easily integrated. Will be great if you take and action soon on this mayor bug to fix it.
@nedbat do you have any updates on this?
Everyone, sorry for the ridiculous regression, and for not attending to it sooner. This is now fixed in fa3b3f5777d0 (bb).
Thank you, can you put it on pypi ?
Great to see that this issue is finally fixed :) Thanks!
Sure, here it is: https://pypi.python.org/pypi/coverage/4.0a3
No branches or pull requests