--coverage fail when the package name is different from the project name
Bug #1298398 reported by
Chmouel Boudjnah
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Testrepository |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
On a personal blog my setup.cfg my project/software name is :
[metadata]
name = package-foo
[...]
[files]
packages =
foo
my package name is actually called foo locally on my filesystem and this is what I would like to test. testrunner force it to have the package from distribution.
http://
Here is patch that add a new option --coverage-
http://
(I think nosetests has a similiar option as well).
Let me know what do you think so I can submit it.
Related branches
lp://staging/~chmouel/testrepository/coverage-package-name
Rejected
for merging
into
lp://staging/~testrepository/testrepository/trunk
- Robert Collins: Needs Fixing
- Marc Abramowitz (community): Approve
-
Diff: 29 lines (+6/-0)1 file modifiedtestrepository/setuptools_command.py (+6/-0)
To post a comment you must log in.
We can do this sure. I think you'll find that pbr has taken over the setup.cfg glue though. IMBW.