Ned,
I still think you're missing the point of my original post. A return
is as good as a break when considering early exit from a loop. The
pylint code only checks for the presence of a break statement, but the
test cases clearly show a case with a return statement. The test
functions even include docstrings which state that.
That's all I'm trying to point out. That I discovered the problem in a
piece of code which could be rewritten to avoid the warning is quite
beside the point.
Skip
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
http://www.voidspace.org.uk/
May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing http://www.sqlite.org/different.html