Marximus Maximus

Found this issue while trying to figure out why my nested test packages all report as top level packages. I, for one, if I went through the trouble to nest...

> Found this issue while trying to figure out why my nested test packages all report as top level packages. I, for one, if I went through the trouble to...

Isn't this just telling coverage.py to generate the lcov.xml file for us? All I use pytest-cov for is to tell coverage.py to do things for me when running pytest. Is...

In addition, it seems to ignore any post-theme coloring effects as well, e.g. the coloring done by BetterComments plugin. Would be great if it could grab that as well as...

FWIW, I am experiencing this just from calling flake8-mypy via flake8 via pre-commit via tox OR when running `flake8` from the command line. I separately tried using a mypy pre-commit...

fwiw, pytest-cov doesn't (yet? https://github.com/pytest-dev/pytest-cov/pull/536) support lcov.xml generation, so it may be worth parsing the coverage.py coverage.xml format; primarily b/c calling pytest+pytest-cov from vscode still only generates the coverage.xml

Suggestion regarding the design above: Directory nodes wrap Packages that are not inside other Packages, such as: ``` ... ... (single explicit file path case: ./y/y2/y3.py) ``` I feel like...

Darn. Came here to request the same thing. If anyone happens to have a recommendation for software that can do the transparent keying, please let me know.

If it's not a tty, it appears that colored output gets lost. stdout is supposed to be the actual things that happened, which is why at least -vv should not...

They are being included in the WRONG PATH in the wheel. That is the bug. If I specify to include the tests folder in the wheel, it should get included....