➜

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 gregory.p.smith
Recipients benjamin.peterson, giampaolo.rodola, gpolo, gregory.p.smith, gvanrossum, michael.foord, pitrou, pupeno, purcell, rhettinger, skip.montanaro
Date 2009-03-31.19:06:10
SpamBayes Score 1.7968986e-09
Marked as misclassified No
Message-id <1238526371.71.0.0307979522547.issue2578@psf.upfronthosting.co.za>
In-reply-to
Content 
def's of the methods changed to be the official assert* names in trunk
r70864.  unittests added to confirm that all known method names continue
to work.

Guido - If we fix 2to3 to fixup unittests that use the fail* method
names to use the assert* names would you be okay with adding the
deprecation warning in 3.1 or should it really wait for 3.2 with a
removal in 3.3?

I'm fine with leaving the deprecation out for 2.7.
History
Date User Action Args
2009-03-31 19:06:12gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, skip.montanaro, rhettinger, purcell, pitrou, giampaolo.rodola, pupeno, benjamin.peterson, gpolo, michael.foord
2009-03-31 19:06:11gregory.p.smithsetmessageid: <1238526371.71.0.0307979522547.issue2578@psf.upfronthosting.co.za>
2009-03-31 19:06:10gregory.p.smithlinkissue2578 messages
2009-03-31 19:06:10gregory.p.smithcreate