Raymond Hettinger rhettin...@users.sourceforge.net 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
Michael Foord mich...@voidspace.org.uk 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
Terry J. Reedy tjre...@udel.edu 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 rep...@bugs.python.org
Ezio Melotti ezio.melo...@gmail.com 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
New submission from Michael Foord mich...@voidspace.org.uk:
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
