Wrong file name for packages (__init__.py)

Issue #437 invalid
Former user created an issue

I'm running nose (v 1.3.7from pypi) with coverage (v 4.0.1 from pypi).

The coverage report doesn't show the right filename for packages (init.py)

.........................................................................................................
Name                                               Stmts   Miss  Cover   Missing
--------------------------------------------------------------------------------
...
rdiffweb/plugins/db_sqlite.py                        199     23    88%   97-103, 163, 187-188, 205, 215-220, 238, 261-264, 294-295, 299, 329-330
rdiffweb/plugins/ldap_auth.py                        134     25    81%   47, 55, 63, 65, 127, 134, 158, 178-182, 186-190, 198-199, 209-210, 215-217, 227
...
--------------------------------------------------------------------------------
TOTAL                                               2763   1377    50%   
----------------------------------------------------------------------

Expected result:

.........................................................................................................
Name                                               Stmts   Miss  Cover   Missing
--------------------------------------------------------------------------------
...
rdiffweb/plugins/db_sqlite/__init__.py                        199     23    88%   97-103, 163, 187-188, 205, 215-220, 238, 261-264, 294-295, 299, 329-330
rdiffweb/plugins/ldap_auth/__init__.py                        134     25    81%   47, 55, 63, 65, 127, 134, 158, 178-182, 186-190, 198-199, 209-210, 215-217, 227
...
--------------------------------------------------------------------------------
TOTAL                                               2763   1377    50%   
----------------------------------------------------------------------

Seams to be related to bug #388.

Comments (3)

  1. Ned Batchelder repo owner

    I don't see this behavior when using "coverage run myprog.py". Are you using the nose plugin? Perhaps the problem is there.

  2. Log in to comment