Prospector: Python Static Analysis for Humans

#1

Post by doismellburning » Sat, Oct 18, 2014, 6:52 PM UTC

Prospector: Python Static Analysis for Humans
blog.landscape.io

Re: Prospector: Python Static Analysis for Humans

#2

Post by sbochins » Sat, Oct 18, 2014, 7:39 PM UTC

I think a better alternative is to use python mode for vim and get all the static analysis checks as you're coding. I tend to do half my development using an IDE (java/scala), but I don't really miss any of those features using this great plugin and vim.

Re: Prospector: Python Static Analysis for Humans

#3

Post by MaxGabriel » Sat, Oct 18, 2014, 8:03 PM UTC

sbochins wrote: post #2

I think a better alternative is to use python mode for vim and get all the static analysis checks as you're coding. I tend to do half my development using an IDE (java/scala), but I don't really miss any of those features using this great plugin and vim.

I don't think the author's tool is in opposition to IDE/plugin based static analysis. For one thing, tools like python-mode for vim (https://github.com/klen/python-mode) call out to libraries like pylint to implement their functionality. Prospector also supports machine readable outputs that IDEs/plugins can use to determine how to display linting issues.

Even if you prefer not to use a command-line based linter, a non-GUI option is essential if you want to do linting with CI. If you run an open source Python project, you can't assume that everyone will use a linter to check for warnings before submitting a PR (and even then, can't assume their linter settings match yours)—but you can check easily lint all PRs using Travis CI or the author's company Landscape.

Re: Prospector: Python Static Analysis for Humans

#4

Post by of » Sat, Oct 18, 2014, 8:23 PM UTC

I haven't tried PyLint -- I use flake8 for static Python analysis: https://pypi.python.org/pypi/flake8

Re: Prospector: Python Static Analysis for Humans

#5

Post by 12ifrb » Sat, Oct 18, 2014, 8:40 PM UTC

GPLv2 License - https://github.com/landscapeio/prospector/blob/master/LICENS...

Warning for those who don't use that license.

Re: Prospector: Python Static Analysis for Humans

#6

Post by the_mitsuhiko » Sat, Oct 18, 2014, 8:56 PM UTC

This "for humans" trend really needs to stop :)

Re: Prospector: Python Static Analysis for Humans

#7

Post by davvid » Sat, Oct 18, 2014, 9:42 PM UTC

12ifrb wrote: post #5

GPLv2 License - https://github.com/landscapeio/prospector/blob/master/LICENS... Warning for those who don't use that license.

If you're using it as an external tool then the license is an irrelevant detail. Folks don't typically do "import pylint" in their code.

Re: Prospector: Python Static Analysis for Humans

#8

Post by joelthelion » Sat, Oct 18, 2014, 9:46 PM UTC

Is there a way to use it with YouCompleteMe/Syntastic?

Re: Prospector: Python Static Analysis for Humans

#9

Post by muyuu » Sat, Oct 18, 2014, 9:46 PM UTC

12ifrb wrote: post #5

GPLv2 License - https://github.com/landscapeio/prospector/blob/master/LICENS... Warning for those who don't use that license.

What's the problem in GPLv2 for a code analysis tool?

Re: Prospector: Python Static Analysis for Humans

#10

Post by jdimov » Sat, Oct 18, 2014, 9:46 PM UTC

This is an awesome tool with a lot of potential and I can't wait to see it evolve. Even though all the hard work is actually done by the 3rd party checkers, THIS ties all these other tools together and makes them an order of magnitude more accessible. Well done!