Message 98692 - Python tracker

➜

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	ezio.melotti, flox, gregory.p.smith
Date	2010-02-01.21:43:32
SpamBayes Score	4.765476e-09
Marked as misclassified	No
Message-id	<1265060614.0.0.0935976543838.issue7832@psf.upfronthosting.co.za>
In-reply-to

Content
The current behavior of "assertSameElements" is not correctly documented. The unit test confirm that it is a tested behaviour. However it seems more useful to provide a method which compares the actual count of each element in both sequences. There's already some use cases in the stdlib test suite. Proposed behavior: Success: assertSameElements([1, None, None], [None, 1, None]) Failure: assertSameElements([1, None, None], [1, 1, 1, None])

The current behavior of "assertSameElements" is not correctly documented.

The unit test confirm that it is a tested behaviour.

However it seems more useful to provide a method which compares the actual count of each element in both sequences.
There's already some use cases in the stdlib test suite.

Proposed behavior:

Success: assertSameElements([1, None, None], [None, 1, None])
Failure: assertSameElements([1, None, None], [1, 1, 1, None])

History
Date	User	Action	Args
2010-02-01 21:43:35	flox	set	recipients: + flox, gregory.p.smith, ezio.melotti
2010-02-01 21:43:33	flox	set	messageid: <1265060614.0.0.0935976543838.issue7832@psf.upfronthosting.co.za>
2010-02-01 21:43:32	flox	link	issue7832 messages
2010-02-01 21:43:32	flox	create