This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vitaly
Recipients docs@python, ezio.melotti, flox, python-dev, ronaldoussoren, vitaly
Date 2016-05-19.20:02:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Python 2.7 documentation is VERY misleading about the functionality of assertItemsEqual. It actually claims to compare not only the counts, but the actual sorted elements themselves. This documentation mislead my group to use this method for comparing the elements. See

   .. method:: assertItemsEqual(actual, expected, msg=None)

      Test that sequence *expected* contains the same elements as *actual*,
      regardless of their order. When they don't, an error message listing the
      differences between the sequences will be generated.

      Duplicate elements are *not* ignored when comparing *actual* and
      *expected*. It verifies if each element has the same count in both
      sequences. It is the equivalent of ``assertEqual(sorted(expected),
      sorted(actual))`` but it works with sequences of unhashable objects as
Date User Action Args
2016-05-19 20:02:32vitalysetrecipients: + vitaly, ronaldoussoren, ezio.melotti, flox, docs@python, python-dev
2016-05-19 20:02:32vitalysetmessageid: <>
2016-05-19 20:02:32vitalylinkissue17866 messages
2016-05-19 20:02:32vitalycreate