Message115852
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) | |
|
Date |
User |
Action |
Args |
2010-09-08 07:12:07 | rhettinger | set | recipients:
+ rhettinger, ezio.melotti, eric.araujo, michael.foord |
2010-09-08 07:12:07 | rhettinger | set | messageid: <1283929927.42.0.993564738731.issue9796@psf.upfronthosting.co.za> |
2010-09-08 07:12:05 | rhettinger | link | issue9796 messages |
2010-09-08 07:12:05 | rhettinger | create | |
|