3 ms·
I'm using pylint daily and usually running it doing "pylint -E" to discard warnings and display errors only. I found it very useful, and never seen a case of an
by tbronchain 10y ago
I'm using pylint daily and usually running it doing "pylint -E" to discard warnings and display errors only.
I found it very useful, and never seen a case of an error that shouldn't be fixes.
I'm probably missing some useful warnings, but it's always better than not using it at all, or getting lost with thousands of them!
- itamarst 10y agoThe problem is the bug that pylint caught that would've gone to production was caught by a warning, not an error. So we could've just used -E but then we'd miss out on some very useful stuff.
- deleted 10y ago[deleted]
- tbronchain 10y agoThat's a fair point I agree. The pylint config files in the article are great, and I will definitely look into it. Pylint -E is more like a quick lazy option to make 80% of the work :)