News for hackers. Stuff that matters.
Re:Automated code review for Python, Django, etc. by wyldfire on Monday April 27, 2015 @10:52AM (#9446647)
If they'd have called it a "static analyzer" they might have had an easier time selling it. Businesses regularly shell out big bucks for C/C++/Java static analysis tools like Coverity, Klocwork, etc.

Static analysis is less likely to yield fruit (design errors and not false positives) in a language like Python. So the bar's definitely higher for these guys than it is for the static analysis tools for static-typed languages.

Re:Automated code review for Python, Django, etc. by ThePhysicist on Monday April 27, 2015 @11:41AM (#9446985)
Good point! You're absolutely right when you say that static analysis is more difficult to do for dynamically typed languages like Python. This is why we develop our own type inference algorithms in order to generate additional knowledge about the code beyond its structure, which in turn allows us to detect more interesting and relevant problems.