This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients ezio.melotti, michael.foord, terry.reedy
Date 2010-08-07.02:19:58
SpamBayes Score 8.24377e-05
Marked as misclassified No
Message-id <1281147601.29.0.624392432529.issue9424@psf.upfronthosting.co.za>
In-reply-to
Content
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 marked as deprecated, and the other methods are not documented.

The plan is:
 1) replace all the occurrences of assertEquals, assertNotEquals, assertAlmostEquals, assertAlmostNotEquals, assert_ in the Python test suite with assertEqual, assertNotEqual, assertAlmostEqual, assertAlmostNotEqual, assertTrue;
 2) deprecate assertEquals, assertNotEquals, assertAlmostEquals, assertAlmostNotEquals, assert_;
 3) patch regrtest.py to raise an error when these methods are used, in order to avoid that they sneak in again in the Python test suite.
History
Date User Action Args
2010-08-07 02:20:01ezio.melottisetrecipients: + ezio.melotti, terry.reedy, michael.foord
2010-08-07 02:20:01ezio.melottisetmessageid: <1281147601.29.0.624392432529.issue9424@psf.upfronthosting.co.za>
2010-08-07 02:19:59ezio.melottilinkissue9424 messages
2010-08-07 02:19:58ezio.melotticreate