3 ms·
FWIW, I like pyflakes because of its design philosophy: """ Pyflakes makes a simple promise: it will never complain about style, and it will try very, very har
by raymondh 10y ago
FWIW, I like pyflakes because of its design philosophy:
"""
Pyflakes makes a simple promise: it will never complain about style, and it will try very, very hard to never emit false positives.
Pyflakes is also faster than Pylint or Pychecker. This is largely because Pyflakes only examines the syntax tree of each file individually. As a consequence, Pyflakes is more limited in the types of things it can check.
"""
- mplewis 10y agoI love Pyflakes. And when I do care about style, I like Flake8 – it has sane defaults and lets me override them on a flexible basis.
- gbog 10y agoI have pyflakes as a vim plugin but it is not enough on big projects, as it will not catch import errors (which are the most common code-breaking errors)
- masklinn 10y agoYep pyflakes is fast, but the tradeoff is that it does relatively little and can't do cross-file inspections or anything somewhat complex. It's also even less well-documented, I have no idea if you can even create a custom flake. pylint's got the advantage that as badly documented as it is creating custom lints is supported and normal.
- shoo 10y agoagreed. i've found pyflakes easier to work with than pylint in terms of setting a minimum standard to enforce (in terms of running it with CI and using it to mark builds as unstable if there are any warnings/errors). pylint warns about various things that arguably aren't actual problems but might be good to clean up in some cases. yes, most of these can be disabled by configuration. on the other hand if you see pyflakes output it tends to indicate something is unambigiously wrong.