`coverage xml` shouldn't bail out on parse error

Issue #396 resolved
Ionel Cristian Mărieș created an issue

I have a module that has to use unsupported syntax (it's only imported if you're on the right python).

But now coverage xml fails cause of that.

$ coverage xml
Couldn't parse '/home/ionel/osp/pytest-benchmark/src/pytest_benchmark/pep418.py' as Python source: 'invalid syntax' at line 47

Can we make it a warning instead?

Comments (11)

  1. Ionel Cristian Mărieș reporter

    Yes. A little bit of extra output doesn't hurt and helps spot potential issues.

  2. Log in to comment