Re: [Zope-dev] SVN: Zope/trunk/ Replaced failUnless with assertTrue and failIf with assertFalse in tests.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote:
Log message for revision 115555: Replaced failUnless with assertTrue and failIf with assertFalse in tests.
Hmm, I don't like the way 'asseertTrue' and 'assertFalse' read -- is there a particular rationale for this change beyond personal taste? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkxfKPkACgkQ+gerLs4ltQ5H+wCfTguS8zUczqF0C7KmEyGywsmh 05EAnAqFFrfvP7pDohhL5cPGJ20Ka+2E =QYtc -----END PGP SIGNATURE-----
On Mon, Aug 9, 2010 at 12:00 AM, Tres Seaver <tseaver@palladion.com> wrote:
Hanno Schlichting wrote:
Log message for revision 115555: Replaced failUnless with assertTrue and failIf with assertFalse in tests.
Hmm, I don't like the way 'asseertTrue' and 'assertFalse' read -- is there a particular rationale for this change beyond personal taste?
The fail* methods are deprecated in Python 2.7's unittest module. Following the "there should only be one way" rule, I guess. More details at http://www.voidspace.org.uk/python/articles/unittest2.shtml#deprecations Hanno
participants (2)
-
Hanno Schlichting -
Tres Seaver