[Python-Dev] r87389 - in python/branches/py3k: Doc/library/unittest.rst Lib/unittest/case.py Misc/NEWS (original) (raw)
R. David Murray rdmurray at bitdance.com
Sun Dec 19 07:52:37 CET 2010
- Previous message: [Python-Dev] r87389 - in python/branches/py3k: Doc/library/unittest.rst Lib/unittest/case.py Misc/NEWS
- Next message: [Python-Dev] r87389 - in python/branches/py3k: Doc/library/unittest.rst Lib/unittest/case.py Misc/NEWS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 18 Dec 2010 20:23:49 -0800, Guido van Rossum <guido at python.org> wrote:
I may be unique, but I fear there is no great answer. On the one hand I almost always code it as e.g. assertEqual(actual, expected), which matches my preference for e.g. "if x =3D=3D 5:" rather than "if 5 =3D=3D x:= ". On the other hand in those assert* functions that show a nice diff of two lists, when reading such a diff my expectation is that "old, new" corresponds to "expected, actual". Which then freaks me out until I realize that I coded it as "actual, expected"... And yet "expected, actual" still looks weird to me. :-(
You aren't unique, I feel the same way. But it seems to me that the most important thing is to be consistent, so that I don't freak out for long.
-- R. David Murray www.bitdance.com
- Previous message: [Python-Dev] r87389 - in python/branches/py3k: Doc/library/unittest.rst Lib/unittest/case.py Misc/NEWS
- Next message: [Python-Dev] r87389 - in python/branches/py3k: Doc/library/unittest.rst Lib/unittest/case.py Misc/NEWS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]