Closed yarbelk closed 9 years ago
Because this plugin relies on the output, it is a pain to deal with these inconsistencies :(
A user with a dated version of py.test
would have issues as well as that flag wasn't introduced until recently.
I wonder if I should just sanitize the output
I just made a small change to sanitize the output from py.test
in commit 992e288d9f24c1eb81395a70b718c9e3992e4a7b
Would you mind trying that out and see if that fixes your (and @gabehollombe) issue? That seems like it would be easier to comply with older versions of py.test
that didn't have that flag.
This works for me (and @gabehollombe)
Issue #11 comment by @gabehollombe where color=yes breaks Pytest.vim
if you have a pytest.ini that sets color=yes, you end up with control characters in your output. this breaks the regex for parsing the results, and you never have any failures as a result. passing --color=no should remove this issue.