[Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses (original) (raw)
Fred Drake fdrake at acm.org
Wed Apr 9 06:56:18 CEST 2008
- Previous message: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses
- Next message: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Apr 8, 2008, at 11:47 PM, Terry Reedy wrote:
I think, however, that the docs should be revised now, for 2.6/3.0. In the list of methods under TestCase Objects, the preferred method of each pair (or triplit) should be given first and the others marked as future deprecations, not recommended for new test code.
+1 !
This kind of information, once known, should be included in all
maintained versions of the documentation so that users can build good
coding habits, or have more time to adjust existing code.
-Fred
-- Fred Drake
- Previous message: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses
- Next message: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]