[issue2578] Figure out what to do with unittest's redundant APIs

Benjamin Peterson report at bugs.python.org
Tue Apr 8 03:01:26 CEST 2008


New submission from Benjamin Peterson <musiccomposition at gmail.com>:

unittest has many redundant APIs (eg. failIf and assertFalse) which can
be phased out in 3.x. We may also want to change the actually methods so
they really do what they say:

if x == y:
   pass
 else:
   raise AssertionError(...)

rather than

 if x != y:
   raise AssertionError(...)

----------
components: Library (Lib)
messages: 65132
nosy: benjamin.peterson
severity: normal
status: open
title: Figure out what to do with unittest's redundant APIs
type: feature request
versions: Python 3.0

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2578>
__________________________________


More information about the Python-bugs-list mailing list