[issue7032] Make assertMultilineEqual default for unicode string comparison in

Michael Foord added the comment: Revision 78116. -- resolution: -> accepted stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue7032] Make assertMultilineEqual default for unicode string comparison in

Michael Foord added the comment: Heh - all ascii would be a better heuristic, or zero null characters perhaps. But 2.X is destined to die anyway so I'm happy for it to only be the default for unicode strings without implementing potentially complex, wrong and slow heuristics. Users can always r

[issue7032] Make assertMultilineEqual default for unicode string comparison in

Antoine Pitrou added the comment: > Because diffing binary data isn't useful... But often it's non-binary data ;) > This is the reason that assertMultilineEqual isn't already the default > for comparing strings - because in Python 2 when you have strings you > don't know if the intention is fo

[issue7032] Make assertMultilineEqual default for unicode string comparison in

Michael Foord added the comment: Because diffing binary data isn't useful... This is the reason that assertMultilineEqual isn't already the default for comparing strings - because in Python 2 when you have strings you don't know if the intention is for them to contain textual information or bin

[issue7032] Make assertMultilineEqual default for unicode string comparison in

Antoine Pitrou added the comment: Why only unicode strings? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7032] Make assertMultilineEqual default for unicode string comparison in

New submission from Michael Foord : unittest.TestCase.assertEqual uses the new type equality functions for comparing containers. In Python 2.7 assertMultilineEqual should be the default comparison method for unicode strings and in Python 3.2 for comparing strings. assertMultilineEqual should o