➜

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 michael.foord
Recipients MarkRoddy, ezio.melotti, georg.brandl, gregory.p.smith, michael.foord, rhettinger
Date 2010-12-21.12:43:03
SpamBayes Score 7.763375e-05
Marked as misclassified No
Message-id <1292935385.43.0.38468922501.issue10242@psf.upfronthosting.co.za>
In-reply-to
Content 
This is committed to 2.7 and 3.2 (using the old name assertItemsEqual in 2.7). As we're well into the beta cycle I don't think we can change the name in 3.2.

The current failure output is very nice for comparing sequences like [1, 2, 3] vs [1, 2, 4]:

AssertionError: Expected, but missing:
    [4]
Unexpected, but present:
    [3]


It is less good for sequences like [2, 2] vs [2, 2, 2]:

AssertionError: Expected, but missing:
    [2]
History
Date User Action Args
2010-12-21 12:43:05michael.foordsetrecipients: + michael.foord, georg.brandl, rhettinger, gregory.p.smith, ezio.melotti, MarkRoddy
2010-12-21 12:43:05michael.foordsetmessageid: <1292935385.43.0.38468922501.issue10242@psf.upfronthosting.co.za>
2010-12-21 12:43:03michael.foordlinkissue10242 messages
2010-12-21 12:43:03michael.foordcreate