While using pylint I have found that having a space between 'print' and
the open bracket is allowed.
Based on the PEP8 pet peeves I would have assumed that 'print ("hello!")'
would have raised the C0326 warning.
Is there a reason why this is not the case? I can't seem to find a post
anywhere talking about allowing this.
There are a few other things that came out of the ashes of Landscape.io
that may or may not make sense to move into PyCQA too:
1) pylint-celery - this one I don’t think anyone uses and it isn’t very
2) pylint-plugin-utils - this is used by pylint-django and pylint-celery as
far as I know, I’m not sure how useful it is outside of that
3) prospector - this is the bigger one, lots of people use this, but I can
understand that it might not be in the same state of mind as the rest of
the PyCQA code :-)
Let me know what you think either way!
Is there a static checker which will catch multiple return types?
Consider this dumb example:
def func(a, b, c):
return (a, b)
I thought pylint had a checker for that, but running with
--rcfile=/dev/null didn't complain about the different types being
returned. Is there perhaps a checker for that which isn't enabled by
default? Or another static tool which will catch it?
I would have expected pyflakes to emit an unused variables warning for "e"
on the following code snippet:
1 / 0
except ZeroDivisionError as e:
Curious if this check can be added.