[issue9424] deprecate unittest.TestCase.assertEquals

Michael Foord added the comment: We aren't talking about *removing* these methods from unittest - but now that we have standardised on assertEqual for the Python test suite it is annoying (particularly for Ezio who changes) when *new* tests are checked in using the old (deprecated-but-not-act

[issue9424] deprecate unittest.TestCase.assertEquals

Raymond Hettinger added the comment: These synonyms have been around a very long time and many test suites have one or the other or both. Nothing good can come from breaking those existing test suites. We don't need to harm our users just to accommodate a stylistic preference. -- a

[issue9424] deprecate unittest.TestCase.assertEquals

Ezio Melotti added the comment: If you are talking about assertNotEquals, assertAlmostEquals, and assertAlmostNotEquals they should go as well (I didn't even know they existed). assert_ is probably used more often, but I'd deprecate it too. Note that in the 2.7 and 3.2 doc assert_ is already m

[issue9424] deprecate unittest.TestCase.assertEquals

Terry J. Reedy added the comment: What about the other duplicate pairs with a preferred choice? Is there too much use of the deprecated choice? -- nosy: +terry.reedy ___ Python tracker _

[issue9424] deprecate unittest.TestCase.assertEquals

New submission from Michael Foord : Now that deprecations are silent by default it would be much less intrusive to deprecate unittest.TestCase.assertEqual We have a persistent issue in the Python test suite of developers using assertEquals when we have standardised on assertEqual. In regrtest