[issue7864] Deprecation markers in unittest docs are unclear

Georg Brandl added the comment: I've added "use ... instead" now in r78018. -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue7864] Deprecation markers in unittest docs are unclear

Justin Lebar added the comment: Oh, I see. I still think a complete sentence would be helpful here, although now that I understand that the colon doesn't mean "use instead" I suppose I'm less confused... -- ___ Python tracker

[issue7864] Deprecation markers in unittest docs are unclear

Ezio Melotti added the comment: > The deprecation warning is confusing, since it appears to suggest that > failUnless is also deprecated. That's exactly what the warning is saying: failUnless() is deprecated since version 3.1. assertTrue and assert_ are ok. -- nosy: +ezio.melotti res

[issue7864] Deprecation markers in unittest docs are unclear

New submission from Justin Lebar : The documentation for assertTrue/assert_/failUnless reads: assertTrue(expr, msg=None) assert_(expr, msg=None) failUnless(expr, msg=None) ... Deprecated since version 3.1: failUnless(). The deprecation warning is confusing, since it appears to suggest t