coverage xml shouldn't bail out on parse error

[nedbat]

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?

---

• Bitbucket: https://bitbucket.org/ned/coveragepy/issue/396

[nedbat]

The -i flag should work for you here, no?

[nedbat]

Original comment by Ionel Cristian Mărieș (Bitbucket: ionelmc, GitHub: ionelmc)

---

Doh! I don't know how I missed it

[nedbat]

Original comment by Ionel Cristian Mărieș (Bitbucket: ionelmc, GitHub: ionelmc)

---

Doooh:)

[nedbat]

Original comment by Ionel Cristian Mărieș (Bitbucket: ionelmc, GitHub: ionelmc)

---

Actually ... shouldn't it show some warnings if --ignore-errors is on?

[nedbat]

You mean show the same messages, but as warnings?

[nedbat]

Original comment by Ionel Cristian Mărieș (Bitbucket: ionelmc, GitHub: ionelmc)

---

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

[nedbat]

Original comment by Matthew Boehm (Bitbucket: mattboehm, GitHub: mattboehm)

---

Looking into this.

[nedbat]

Original comment by Matthew Boehm (Bitbucket: mattboehm, GitHub: mattboehm)

---

Pull request: #8

[nedbat]

Applied and fixed in 551dc23 (bb).