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 gregory.p.smith
Recipients ezio.melotti, georg.brandl, gregory.p.smith, michael.foord, r.david.murray, rbcollins, rhettinger, serhiy.storchaka, vitaly
Date 2016-05-23.20:49:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464036565.54.0.783670753737.issue27071@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not against adding a new name if it makes glorious sense, but we should not remove the old names from unittest as that causes unnecessary pain (based on past experience).

assertCountEqual does make sense in terms of the "equivalent to" context from the docs.  Thought I agree with you, its meaning is generally not obvious and must be looked up to be understood. https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertCountEqual

assertUnorderedEqual is a reasonable name, but I don't find significantly better than assertCountEqual from a "never read the docs, just reading the code" understandability point of view.  It makes me wonder "unordered what?"

that's a vote of -0 for the status quo.
History
Date User Action Args
2016-05-23 20:49:25gregory.p.smithsetrecipients: + gregory.p.smith, georg.brandl, rhettinger, rbcollins, ezio.melotti, r.david.murray, michael.foord, serhiy.storchaka, vitaly
2016-05-23 20:49:25gregory.p.smithsetmessageid: <1464036565.54.0.783670753737.issue27071@psf.upfronthosting.co.za>
2016-05-23 20:49:25gregory.p.smithlinkissue27071 messages
2016-05-23 20:49:25gregory.p.smithcreate