Raymond Hettinger <rhettin...@users.sourceforge.net> added the comment:
Just focus on the table for assert* methods. This is the one category that users will need to look-up over and over again. The goal is to make the docs more usable, not more voluminous. Also, I suggest finding meaningful groupings (don't stick with alpha order) and including a short plain assert-statement equivalents to show what the methods actual do (this is important because many are new, some are obscure, and not all have obvious semantics): | assertEqual(x, y) | assert x == y | | assertGreaterThan(x, y) | assert x > y | | assertItemsEqual(act, exp) | assert sorted(exp) == sorted(act) | ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9796> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
