Message 63411 - Python tracker

➜

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	jcea
Recipients	georg.brandl, jcea, purcell, rhettinger
Date	2008-03-09.10:10:08
SpamBayes Score	0.09673188
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
I noted the issue while working in bsddb3 module. If failed in python2.3 because some tests were using "assertTrue". I had to dig where that method came from (time lost!) and found that a) it was added in python 2.4 and b) it is not documented. Since "assertTrue" use is "in the wild", being undocumented is a inconvenience. Moreover, I think "assertTrue" is far more intuitive and cleaner than "assert_" or "failUnless". A personal impression, of course. Symmetric with "assertEqual" and so, would be nice. I won't insist, in any case :-)

I noted the issue while working in bsddb3 module. If failed in python2.3
because some tests were using "assertTrue". I had to dig where that
method came from (time lost!) and found that a) it was added in python
2.4 and b) it is not documented.

Since "assertTrue" use is "in the wild", being undocumented is a
inconvenience. Moreover, I think "assertTrue" is far more intuitive and
cleaner than "assert_" or "failUnless". A personal impression, of
course. Symmetric with "assertEqual" and so, would be nice.

I won't insist, in any case :-)

History
Date	User	Action	Args
2008-03-09 10:10:16	jcea	set	spambayes_score: 0.0967319 -> 0.09673188 recipients: + jcea, georg.brandl, rhettinger, purcell
2008-03-09 10:10:16	jcea	set	spambayes_score: 0.0967319 -> 0.0967319 messageid: <[email protected]>
2008-03-09 10:10:10	jcea	link	issue2249 messages
2008-03-09 10:10:08	jcea	create