Issue 8351: Suppress large diffs in unitttest.TestCase.assertSequenceEqual() (original) (raw)

Issue8351

Created on 2010-04-08 23:36 by flub, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg102653 - (view)	Author: Floris Bruynooghe (flub)	Date: 2010-04-08 23:36
This patch adds the ability to suppress large diffs in the failure message of TestCase.assertSequenceEqual(). The maximum size of the diff is customisable as an new keyword parameter with hopefully a sensible default.
msg107129 - (view)	Author: Michael Foord (michael.foord) *	Date: 2010-06-05 11:25
Slightly modified version committed revision 81728. (It truncates large diffs rather than omitting them and allows max_diff to be None - meaning no maximum.) Needs some extended tests and needs documenting.
msg107131 - (view)	Author: Michael Foord (michael.foord) *	Date: 2010-06-05 12:11
Modified again in revision 81739. No longer uses a new argument, but a class attribute instead. All assert methods that generate failure messages with difflib truncate messages.
msg107135 - (view)	Author: Michael Foord (michael.foord) *	Date: 2010-06-05 13:40
Modified again in revision 81752. Assertion methods now inform you when omitting an excessively long diff.
msg107136 - (view)	Author: Michael Foord (michael.foord) *	Date: 2010-06-05 14:00
Still some tests and documentation needed. Leaving issue open until it is done. (Also needs backporting to unittest2...)
msg107137 - (view)	Author: Michael Foord (michael.foord) *	Date: 2010-06-05 14:06
Note that we also have a bit of a performance issue in prettyprint / difflib when the diffs are very big. It can spend a minute or more constructing the diff - only to throw it away because it is too big...