pylint #52022 warning not triggered when it should [resolved]

a = 42
def foo():
    return 42
a == foo()

I'd expect pylint to also warn in this case:

W:  5: Statement seems to have no effect
prioritynormal
typeenhancement
appeared in<not specified>
done in0.23.0
load0.300
load left0.000
closed by<not specified>

Workflow history

from state (3)to statecommentdateUser
validation pendingresolved2011/03/10 11:39sthenault
donevalidation pending

version published

2011/01/13 21:38sthenault
opendone2010/12/13 10:16eanclin

Comments

  • 2010/12/09 10:20, written by eanclin | reply to this comment

    well, function calls usually have side effects; so do you expect pylint to recognize that some function has no side effect? I would suggest that we add a new warning:

    W : Expression "a == foo()" is not assigned to anything

    It would be easy to implement and would also occur if the function call has indeed an effect.

(add comment)
Ticket #52022 - latest update on 2011/03/10, created on 2010/12/08 by Aurelien Campeas