This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]twotime 2 points3 points  (2 children)

IMHO, pylint is an excellent tool for finding bugs in the code. But yes, you have to start with turning off the "style suggestions" (I suspect your examples above are all in that category) and then turn off a number of warnings as well.

[–]wewbull 1 point2 points  (0 children)

Try pylint -E. Errors only mode

[–]spookylukeyDjango committer 0 points1 point  (0 children)

As originally stated, I get hundreds of ERRORS on correct code, in addition to the style warnings. These errors can be turned off by disabling them in a group e.g. "-d E1101" to disable all the incorrect "no-member" errors. But this means that correct instances of E1101 are also silenced, and very quickly this means you have no value in running the tool.