[issue7864] Deprecation markers in unittest docs are unclear
Ezio Melotti
report at bugs.python.org
Sat Feb 6 05:30:55 CET 2010
Ezio Melotti <ezio.melotti at gmail.com> 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
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7864>
_______________________________________
More information about the Python-bugs-list
mailing list