Re: [Zope-dev] SVN: zope.tal/trunk/src/zope/tal/dummyengine.py assert isn't a function, using parens will cause the two arguments to be treated as a 2-tuple, hence always true.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: > Tres Seaver wrote: >> Matthew Wilkes wrote: >>> Log message for revision 93717: >>> assert isn't a function, using parens will cause the two arguments to be >>> treated as a 2-tuple, hence always true. >>> Changed: >>> U

Re: [Zope-dev] SVN: zope.tal/trunk/src/zope/tal/dummyengine.py assert isn't a function, using parens will cause the two arguments to be treated as a 2-tuple, hence always true.

Tres Seaver wrote: > Matthew Wilkes wrote: >> Log message for revision 93717: >> assert isn't a function, using parens will cause the two arguments to be >> treated as a 2-tuple, hence always true. > >> Changed: >> U zope.tal/trunk/src/zope/tal/dummyengine.py > >> -=- >> Modified: zope.tal

Re: [Zope-dev] SVN: zope.tal/trunk/src/zope/tal/dummyengine.py assert isn't a function, using parens will cause the two arguments to be treated as a 2-tuple, hence always true.

On Mon, Dec 8, 2008 at 12:26 PM, Tres Seaver <[EMAIL PROTECTED]> wrote: > A better fix would be to strip outthe 'assert' keyword everywhere, and > use 'self.failUnless' / 'self.failIf' instead: that would allow getting > rid of the "backsplash", as well. Yep. Another reason not to use "assert" i

Re: [Zope-dev] SVN: zope.tal/trunk/src/zope/tal/dummyengine.py assert isn't a function, using parens will cause the two arguments to be treated as a 2-tuple, hence always true.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Wilkes wrote: > Log message for revision 93717: > assert isn't a function, using parens will cause the two arguments to be > treated as a 2-tuple, hence always true. > > Changed: > U zope.tal/trunk/src/zope/tal/dummyengine.py > > -=- >