R. David Murray added the comment:
Thanks, fixed. Appears to have been a mistake made when we refactored from
expected/actual to first/second.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> behavior
__
Roundup Robot added the comment:
New changeset ff52583a5576 by R David Murray in branch '2.7':
#14832: 'first' now really refers to first arg in unittest assertItemsEqual
http://hg.python.org/cpython/rev/ff52583a5576
--
nosy: +python-dev
___
Python t
New submission from Kylotan :
I have the following line in a unit test in 2.7.3:
self.assertItemsEqual(['a', 'b', 'c'], ['a', 'b', 'c', 'd'])
I expect this output:
AssertionError: Element counts were not equal:
First has 0, Second has 1: 'd'
Instead I get this output:
Assert