Re: [Python-Dev] unittest's redundant assertions: assertsvs. failIf/Unlesses

On Tue, Apr 8, 2008 at 9:56 PM, Fred Drake fdrake@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.