6
Since you mention that it is only happening when you run coverage
it is quite possible that it is happening because coverage
is not using your virtualenv, but your global python installation instead.
A question with similar issue has been posted here before – Running coverage inside virtualenv
Apparently, you need to install coverage
in your virtualenv as well for it work as expected.
Source:stackexchange.com