Bug 388443 – dev-python/nose should have "coverage" USE flag to control dependency on dev-python/coverage

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jeroen Roovers (RETIRED) 2011-10-25 12:49:09 UTC]

test_pickle_configured (test_config.TestNoseConfig) ... nose.plugins.cover: ERROR: Coverage not available: unable to import coverage module
nose.plugins.cover: ERROR: Coverage not available: unable to import coverage module
nose.plugins.cover: ERROR: Coverage not available: unable to import coverage module
[...]

[Comment 1 Ian Delaney (RETIRED) 2011-12-02 05:40:20 UTC]

yes, confirmed.

        doc? ( >=dev-python/sphinx-0.6 )
        test? ( >=dev-python/coverage-3.4 )"

[Comment 2 Arfrever Frehtes Taifersar Arahesis 2011-12-18 22:20:25 UTC]

coverage dependency is optional. Maybe there should be a USE flag.
Tests, which use coverage, should be skipped, when coverage isn't available.

[Comment 3 Arfrever Frehtes Taifersar Arahesis 2011-12-19 07:19:14 UTC]

Actually there is no bug in test suite. Tests, which need dev-python/coverage, are already skipped when dev-python/coverage isn't installed. "ERROR: Coverage not available" doesn't mean that any tests failed. If any test failed, then selftest.py would have non-zero exit status, which would trigger call to die(). (selftest.py has proper exit status. All tests pass with CPython 3.2, but currently 4 tests fail with CPython 3.3, which triggers call to die().)

("coverage" USE flag has been added in dev-python/nose-1.1.2::progress. It controls both run-time and build-time dependency on dev-python/coverage.)