➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, georg.brandl, jcea, purcell, rhettinger
Date 2008-03-09.13:45:53
SpamBayes Score 0.008072504
Marked as misclassified No
Message-id <1205070355.55.0.560032153411.issue2249@psf.upfronthosting.co.za>
In-reply-to
Content 
FWIW, grepping through Lib/test reveals the following statistics:

assertFalse: 83
assertTrue: 97
failUnless: 684
assert_: 1977

Not having assertTrue/assertFalse methods in the Library Reference does 
not discourage people from using them given that they show up without 
any warning in help().  (Moreover, assertTrue shows up before assert_.)

I would say it should be documented.  After all it would only take a two 
line patch (see attached). 

(I agree with OP that assertTrue is clearer than assert_ . Although I 
know that '_' is only there to avoid a conflict with the assert keyword,   
assert_ always stand out as different from the other TestCase methods.)
History
Date User Action Args
2008-03-09 13:45:56belopolskysetspambayes_score: 0.0080725 -> 0.008072504
recipients: + belopolsky, georg.brandl, rhettinger, jcea, purcell
2008-03-09 13:45:55belopolskysetspambayes_score: 0.0080725 -> 0.0080725
messageid: <1205070355.55.0.560032153411.issue2249@psf.upfronthosting.co.za>
2008-03-09 13:45:54belopolskylinkissue2249 messages
2008-03-09 13:45:54belopolskycreate