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 eric.araujo, ezio.melotti, flox, gregory.p.smith, michael.foord
Date 2010-02-02.12:55:28
SpamBayes Score 0.0002210909
Marked as misclassified No
Message-id <1265115330.73.0.37381979234.issue7832@psf.upfronthosting.co.za>
In-reply-to
Content
Damn. If assertSameElements has already shipped with the existing implementation then we can't change it. The documentation really needs clarifying to make it clear that it ignores duplicates.

I would be happy with a 'check_order' argument to assertSequenceEqual defaulting to True, and slightly prefer that to a new method.

FWIW the http://code.google.com/p/python-unittest-backport/ project is quite out of date. I am intending to do my own port (before PyCon) that subclasses unittest so that it can interoperate with code using the Python 2.4-2.6 standard library unittest. I may get in touch with the project owner to see if I can join him on his project.
History
Date User Action Args
2010-02-02 12:55:30michael.foordsetrecipients: + michael.foord, gregory.p.smith, ezio.melotti, eric.araujo, flox
2010-02-02 12:55:30michael.foordsetmessageid: <1265115330.73.0.37381979234.issue7832@psf.upfronthosting.co.za>
2010-02-02 12:55:29michael.foordlinkissue7832 messages
2010-02-02 12:55:28michael.foordcreate