[Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses (original) (raw)
Guido van Rossum guido at python.org
Wed Apr 9 18:37:50 CEST 2008
- Previous message: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses
- Next message: [Python-Dev] Changing all network-oriented tests to facilitate (virtually unlimited) parallel test execution [Issue#: 2550]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 8, 2008 at 9:56 PM, Fred Drake <fdrake at acm.org> wrote:
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.
Great point, Fred! This sounds like a general strategy that we might employ more often -- when deprecating something, the first step ought to be to document the best practice.
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses
- Next message: [Python-Dev] Changing all network-oriented tests to facilitate (virtually unlimited) parallel test execution [Issue#: 2550]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]