[issue35500] Align expected and actual calls on mock.assert_called_with error message

[Terry J. Reedy]

Terry J. Reedy <tjreedy at udel.edu> added the comment:

We don't usually wrap error messages, but this is plausible.  With the addition to the first line, we don't need to repeat 'call'.  We can line things up without violating the PEP 8 recommendation against doing so with spaces.  Also, the convention is to not capitolize the phrase after ':'.

AssertionError: expected call not found.
Expect: mock(2, 3)
Actual: mock(1, 2)

----------
nosy: +terry.reedy

______________________________________________
Python tracker <cpython at roundup.psfhosted.org>
<https://bugs.python.org/issue35500>
______________________________________________