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 ezio.melotti
Recipients brett.cannon, ezio.melotti, michael.foord, pitrou, r.david.murray, rhettinger
Date 2010-11-04.00:27:02
SpamBayes Score 9.660233e-06
Marked as misclassified No
Message-id <1288830424.01.0.720043508788.issue10273@psf.upfronthosting.co.za>
In-reply-to
Content
An alternative would be adding check_order and check_duplicates to assertSameElements and de-deprecate it.

Python 2.7 could be left unchanged because it's too late to add/rename/deprecate methods (it has assertItemsEqual but not assertSameElements). Py3.2 would also be unchanged (assertItemsEqual and the deprecation of assertSameElements are both new in 3.2, assertSameElements has been introduced in 3.1).
They would end up with two different methods though.

The assertSameElements name seems quite good, and providing extra args will make it more flexible (it will cover all the 4 cases listed in msg100685) and the behavior would be clear without clumsy method names.
History
Date User Action Args
2010-11-04 00:27:04ezio.melottisetrecipients: + ezio.melotti, brett.cannon, rhettinger, pitrou, r.david.murray, michael.foord
2010-11-04 00:27:04ezio.melottisetmessageid: <1288830424.01.0.720043508788.issue10273@psf.upfronthosting.co.za>
2010-11-04 00:27:02ezio.melottilinkissue10273 messages
2010-11-04 00:27:02ezio.melotticreate