coverage xml shouldn't bail out on parse error #396
Description
Originally reported by Ionel Cristian Mărieș (Bitbucket: ionelmc, GitHub: ionelmc)
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?