[issue35955] unittest assertEqual reports incorrect location of mismatch

Karthikeyan Singaravelan added the comment: Sorry to comment on a closed issue. I see the following behavior with difflib.ndiff which is used under the hood by unittest. The strings that differ by '-' and 'w' generate different output compared to 'a' and 'w'. I find the output for diff

[issue35955] unittest assertEqual reports incorrect location of mismatch

Jason R. Coombs added the comment: I was able to replicate the issue using pytest and not unittest, so I've [reported the issue with that project](https://github.com/pytest-dev/pytest/issues/4765). -- ___ Python tracker

[issue35955] unittest assertEqual reports incorrect location of mismatch

Change by Jason R. Coombs : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35955] unittest assertEqual reports incorrect location of mismatch

Jason R. Coombs added the comment: I should acknowledge that I'm using pytest here also... and pytest may be the engine that's performing the reporting of the failed assertion. In fact, switching to simple assertions, I see the same behavior, so I now suspect the issue may lie with pytest

[issue35955] unittest assertEqual reports incorrect location of mismatch

New submission from Jason R. Coombs : In [this job](https://travis-ci.org/jaraco/cmdix/jobs/491246158), a project is using assertEqual to compare two directory listings that don't match in the group. But the hint markers pointing to the mismatch are pointing at positions that match: E