Home Original page

[Python-Dev] Issue #26204: compiler now emits a SyntaxWarning on constant statement

MRAB python at mrabarnett.plus.com
Mon Feb 8 20:41:12 EST 2016 
On 2016-02-09 00:53, Guido van Rossum wrote:
> The warning for 'assert (cond, msg)' was specifically put in because
> this is a nasty trap. It's *always* a mistaken attempt to write
> 'assert cond, msg' -- usually in an attempt to break a long line
> without using a backslash. I'd actually consider promoting it to a
> syntax error rather than removing the warning.
>
> Compared to other "lint warnings" this one is much nastier -- it is
> also much more certain that it is a mistake. (Much more certain than
> e.g. an undefined variable, which could still be legitimate code due
> to dynamic updates to globals() or builtins.)
Would there be less chance of confusion if there were some kind of 
syntax such as "assert cond with msg"?
More information about the Python-Dev mailing list