New submission from Pete Zaitcev:
When using an assert such as self.assertEquals(tester(), expected), an error
message suggests wrong argument order (as in, not the order in examples in the
documentation). Apparently this is confusing enough that OpenStack even opened
a whole bunch of bugs
R. David Murray added the comment:
Testtools is not part of the stdlib. Are you saying there is a bug in the
stdlib assertEqual? If so, can you demonstrate the bug using just stdlib-based
code?
--
nosy: +r.david.murray
___
Python tracker
Pete Zaitcev added the comment:
Oh, indeed. The printout is in testtools only. The unittest prints this:
[zaitcev@guren xxx]$ python3 -c 'import nose; nose.main()'
F
==
FAIL: test_testEquals (testic.TestConfigTrueValue)
Changes by R. David Murray rdmur...@bitdance.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20798
___
___
