[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Chris Jerdonek added the comment: When I first created the issue, the title I chose was about unittest ("unittest assertEqual difference output foiled by newlines"), but someone else changed it for some reason. You're welcome to change it back to something more like the original.

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Karthikeyan Singaravelan added the comment: Looking at the patch and the relevant function this doesn't seem to be a problem with difflib.ndiff but with unittest's display algorithm. This causes confusion about the issue and I propose changing the subject to reflect this unless difflib

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Change by Karthikeyan Singaravelan : -- nosy: +xtreak versions: +Python 3.7, Python 3.8 -Python 3.5, Python 3.6 ___ Python tracker ___

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Changes by Raymond Hettinger : -- nosy: +loewis, tim.peters ___ Python tracker ___

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Adrian Chan added the comment: I've attached a potential fix for this issue. While trying to fix this, I noticed that I coudn't assume that I just need to ensure that each line has a newline. If I always ensure each line in diffline has a newline, then the fourth test in

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

Changes by ppperry : -- components: -Tests title: unittest assertEqual difference output foiled by newlines -> difflib.ndiff produces unreadable output when input missing trailing newline ___ Python tracker