-
-
Notifications
You must be signed in to change notification settings - Fork 433
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
Create Way to force package even if filepath exists #268
Create Way to force package even if filepath exists #268
Comments
What about supporting a Or allowing to specify For reference, the code is: coveragepy/coverage/inorout.py Lines 133 to 137 in 4113a32
|
I didn't know this issue existed, though yeah I've fought with this in the past -- FWIW, I count this as yet another reason not to run tox out of cwd. That's perhaps a less desirable internal (to coverage) solution if it means "tell users of coverage to change their tox.ini", but just to chime in, yeah, that's exactly what I do and recommend. (So I have (EDIT: sample here if you want something runnable: https://github.com/Julian/regret/blob/main/tox.ini#L33-L42 and https://github.com/Julian/regret/blob/main/.coveragerc#L4, and yeah |
Fixed in ecd6ab1 |
This is now released as part of coverage 5.3. |
Originally reported by Donald Stufft (Bitbucket: dstufft, GitHub: dstufft)
When using tox to run tests the preferred way to run tests creates throw away virtual environments and installs the package to be tested into them. This means that the code to be running is actually inside .tox/venvname/lib/pythonX.Y/site-packages/library.
Normally coverage.py could support this BUT when doing --source library it sees the library/ directory in the current directory (which isn't being used) and doesn't do the package resolution. This leads to 0% coverage reports always when using tox. It would be great if there was a way to say "No really this is a package".
The text was updated successfully, but these errors were encountered: