Michael Foord mich...@voidspace.org.uk added the comment:
In Python 3.2 assertItemsEqual has been replaced with assertCountEqual that has
a completely different implementation and error format. The implementation and
error output will be backported to the assertItemsEqual method of 2.7 (and to
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9977
___
___
Python-bugs-list
Terry J. Reedy tjre...@udel.edu added the comment:
If I understand correctly, you are requesting that .assertItemsEqual only use
the 2nd (multiset comparison) method, so that if one want the first method, one
should directly call .assertSequenceEqual(sorted(a), sorted(b)).
This seems
Matthew Woodcraft matt...@woodcraft.me.uk added the comment:
Terry J. Reedy wrote:
If I understand correctly, you are requesting that .assertItemsEqual
only use the 2nd (multiset comparison) method, so that if one want the
first method, one should directly call .assertSequenceEqual(sorted(a),
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9977
___
___
Python-bugs-list
New submission from Matthew Woodcraft matt...@woodcraft.me.uk:
TestCase.assertItemsEqual uses two different techniques to describe the
differences in the inputs that it compares.
If the inputs are sortable, it sorts them and then uses
assertSequenceEqual to describe the difference between them
Changes by Michael Foord mich...@voidspace.org.uk:
--
assignee: - michael.foord
components: +Library (Lib)
versions: +Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9977
___
