Ned Batchelder
Ned Batchelder
@undera Use the `--show-contexts` option to the "coverage html" command. There isn't a way to specify this option through pytest-cov.
@ssbarnea this sounds like a good example of why pytest-cov should do less: it's hard to control the reporting options when you consider all the different ways pytest runs. Would...
This could be useful for people not using pytest-cov. Are you interested in pursuing an implementation that goes direct to coverage.py?
You don't need to add anything to pytest-cov. Just run `coverage lcov` after you run pytest.
This is really about [coverage.py](https://github.com/nedbat/coveragepy)'s behavior. But I'm not sure what can be done about it. Coverage isn't going to be able to analyze the universe of possible values and...
This kind of analysis is well outside what coverage.py does. It currently does nothing about data values or types. I won't say it can't be done, but it would be...
@patti-c Coverage 5.0 is new, and we are working out the problems. We are not going to pin coverage in pytest-cov, instead we will be trying to fix the problems...
I believe this is the same as https://github.com/nedbat/coveragepy/issues/703. The bug only occurs with Python 3.6.0, it is fixed in Python 3.6.1. If this isn't your scenario, please re-open the issue...
Coverage will read settings from setup.cfg, or tox.ini, or pyproject.toml files. There's no need to add another option to an already cluttered command line.
@roipoussiere You don't have any of these files? setup.cfg, tox.ini, pyproject.toml?