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 flox
Recipients flox
Date 2012-08-29.13:18:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1346246299.41.0.924919509525.issue15810@psf.upfronthosting.co.za>
In-reply-to
Content
When writing unittest, I noticed that I need to uses assertSequenceEqual explicitly when comparing sequences of different kinds.

If I only use the plain assertEqual, it does not generate pretty diffs.

On second thought, I think it could be fixed in unittest to use assertSequenceEqual when isinstance(arg, (tuple, list)) or isinstance(arg, collections.Sequence) is True.
History
Date User Action Args
2012-08-29 13:18:19floxsetrecipients: + flox
2012-08-29 13:18:19floxsetmessageid: <1346246299.41.0.924919509525.issue15810@psf.upfronthosting.co.za>
2012-08-29 13:18:18floxlinkissue15810 messages
2012-08-29 13:18:18floxcreate