Raymond Hettinger <raymond.hettin...@gmail.com> wrote: > I looked at this again and think we should just remove > assertItemsEqual() from Py3.2 and dedocument it in Py2.7. It is listed > as being new in 3.2 so nothing is lost.
One thing that would be lost is that correct Python 2.7 code using assertItemsEqual would no longer run on 3.2. > The sole benefit over the more explicit variants like > assertEqual(set(a), set(b)) and assertEqual(sorted(a), sorted(b)) is > that it handles a somewhat rare corner case where neither of those > work (unordered comparison of non-compable types when you do care > about duplicates). Another benefit is that it gives better descriptions of differences. See http://bugs.python.org/issue9977 for an example. -M- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
