The Python assert statement is not a function, and treating it as such - i.e.:
assert (a == b, "The things weren't equal!")
results in evaluating a 2-element tuple as a boolean, thus, it's approximately the same as 'assert True', i.e. a no-op.
Python 2.6 recognizes this flaw, and adds a SyntaxWarning to report this case. Thus, by running:
find -name \*.py -type f | xargs python2.6 -m py_compile
I've located all instances of the problem in the Launchpad source.
Here's a branch applying the requisite syntax fixes.
« Back to merge proposal
The Python assert statement is not a function, and treating it as such - i.e.:
assert (a == b, "The things weren't equal!")
results in evaluating a 2-element tuple as a boolean, thus, it's approximately the same as 'assert True', i.e. a no-op.
Python 2.6 recognizes this flaw, and adds a SyntaxWarning to report this case. Thus, by running:
find -name \*.py -type f | xargs python2.6 -m py_compile
I've located all instances of the problem in the Launchpad source.
Here's a branch applying the requisite syntax fixes.