Nick Coghlan <[EMAIL PROTECTED]> writes: > What did you think of the "check" idea at the end of the email? > > Test assertions: > check(x).almost_equal(y) > check(x).is_(y) > check(x).in_(y) > check(x).equals(y) > > Test negative assertions: > check(x).not_almost_equal(y) > check(x).is_not(y) > check(x).not_in(y) > check(x).not_equal(y)
-1 'check' is even less explicit about what will happen than 'assert'. At least the latter has existing programming-language connotations of "fail immediately if not true", which 'check' lacks. -- \ “I used to work in a fire hydrant factory. You couldn't park | `\ anywhere near the place.” —Steven Wright | _o__) | Ben Finney _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
