Repository navigation
Coverage data isn't properly reported for Python 3+ #49
Description
I'm wondering if this issue is due to an issue with Pynsive's module loading process as this resembles the issue that I fixed in Pynsive to support coverage in Python 2.7.
Coverage report for Python 3.4.x
py34 runtests: commands[1] | coverage report -m
Name Stmts Miss Cover Missing
------------------------------------------------
lplight/__init__ 0 0 100%
lplight/client 54 54 0% 1-101
lplight/models 124 124 0% 1-143
------------------------------------------------
TOTAL 178 178 0%
_________________________________________
Coverage report for Python 2.7.x
py27 runtests: commands[1] | coverage report -m
Name Stmts Miss Branch BrMiss Cover Missing
--------------------------------------------------------------
lplight/__init__ 0 0 0 0 100%
lplight/client 54 54 12 12 0% 1-101
lplight/models 124 0 4 1 99% 8->7
--------------------------------------------------------------
TOTAL 178 54 16 13 65%
Activity
Fixing issue with import order when using in Python 3
jmvrbanac commentedon Sep 24, 2015
Switching to Pike for module loading (in 0.3.0) fixed the majority of the problems. However, there is still an outstanding problem with getting Python 3 coverage via
specter --coverage.Workaround
coverage run -m specter