[Python-Dev] Proposed unittest changes (original) (raw)

Steve Holden steve at holdenweb.com
Mon Jul 14 14:45:06 CEST 2008

Ben Finney wrote:

Nick Coghlan <ncoghlan at gmail.com> writes:

Ben Finney wrote: The problem is, that makes it quite inconsistent with other "not" uses (such as "assertnotequal", "assertnotin", etc.) I would really prefer that all these "not" uses be gramatically consistent for predictability. Is this a case where "assertisnot" should exist alongside "assertnotis"? If we can flip the word order in the language syntax, we can sure as heck flip it in a method name :) To be clear, I take it you're in favour of the following names (with no aliases): assertequal assertnotequal assertis assertisnot assertin assertnotin assertalmostequal assertnotalmostequal and so on; i.e. that 'assertisnot' breaks the obvious pattern set by the others, in the interest of matching Python's 'is not' grammar. Well, I'd have said "in the interest of reading correctly in English", though I have to acknowledge this may not be an issue for many Python users whose first language not is English. "assert_not_is" is just dissonant to my ears.

regards Steve

Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/

More information about the Python-Dev mailing list