New submission from Michael Foord <mich...@voidspace.org.uk>: The unittest documentation, argument names and implementation need to be consistent about the order of (actual, expected) for TestCase.assert methods that take two arguments.
This is particularly relevant for the methods that produce 'diffed' output on failure - as the order determines whether mismatched items are missing from the expected or additional to the expected. The documentation, signatures and implementation of all two argument asserts need to be checked to ensure they are the same and implemented correctly. Personally I prefer (actual, expected). ---------- assignee: michael.foord components: Documentation, Library (Lib) messages: 122752 nosy: michael.foord priority: normal severity: normal status: open title: Consistency in unittest assert methods: order of actual, expected versions: Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10573> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
