-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve AssertionError
error message for sequences inside dictionaries
#12717
base: main
Are you sure you want to change the base?
Changes from all commits
e60e7ee
1d3d99e
5210674
6c5a720
770d8ba
a1b0239
41c48fb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Improves `AssertionError` error message for sequences inside dictionaries when not running verbose mode. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -354,7 +354,7 @@ def _compare_eq_iterable( | |
def _compare_eq_sequence( | ||
left: Sequence[Any], | ||
right: Sequence[Any], | ||
highlighter: _HighlightFunc, | ||
highlighter: _HighlightFunc | Callable[[str], str], | ||
verbose: int = 0, | ||
) -> list[str]: | ||
comparing_bytes = isinstance(left, bytes) and isinstance(right, bytes) | ||
|
@@ -501,10 +501,19 @@ def _compare_eq_dict( | |
if diff: | ||
explanation += ["Differing items:"] | ||
for k in diff: | ||
left_val = left[k] | ||
right_val = right[k] | ||
if issequence(left_val) and issequence(right_val): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure I like this approach, given this is really only specific for sequences inside dictionaries... this is not general because really we could have anything in there, for example other dicts or dataclasses, each with their own custom diff code... 🤔 The core of the original issue was the fact that it was truncating the diff. One idea is to not truncate anything when computing the diff, however truncation is there for a reason, to avoid dumping MBs of text in case of large data structures... I'm a bit -1 on this solution, given it only fixes a very specific use case and makes the code slightly worse, but I don't have a definitive suggestion either. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah I initially thought we could take all the cases in
Besides this though, I figured sequence comparisons would be the most likely use case, and it'd be worth having it there despite the bit of complexity. I could be wrong though! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. An alternative method might be to figure out a truncated diff for the other data types such as a simple |
||
expl = _compare_eq_sequence( | ||
left_val, right_val, lambda item: item, verbose | ||
) | ||
explanation += [highlighter(saferepr({k: "".join(expl)}))] | ||
continue | ||
|
||
explanation += [ | ||
highlighter(saferepr({k: left[k]})) | ||
highlighter(saferepr({k: left_val})) | ||
+ " != " | ||
+ highlighter(saferepr({k: right[k]})) | ||
+ highlighter(saferepr({k: right_val})) | ||
] | ||
extra_left = set_left - set_right | ||
len_extra_left = len(extra_left) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not really be needed, given
_HighlightFunc
is compatible withCallable[[str], str]
: