Hi all, author of Prospector here. It's definitely not an alternative to pylint or flake8, it's just a convenience wrapper. The entire point was just to make it a bit easier to get started as not everyone wants to spend the time configuring every tool. The idea is to be a "gateway drug" to bridge the gap between no code quality tooling and having everything configured perfectly for your particular project.
As a "code quality newbie" you're sort of the target market, but I encourage you to dig deeper if you get benefits from prospector as you will get more benefits by tuning each tool yourself to fit your particular style of coding! Cheers, Carl On 22 October 2015 at 21:27, Linus Törngren <li...@etnolit.se> wrote: > I do, but as I understand it prospector aggregates (optionally) the results > of pylint, pyflakes, mccabe, dodgy, pep8 and pep257. It also has a bunch of > profiles with settings for the different tools. That’s attractive for a code > quality newbie like me. > > 22 okt. 2015 kl. 21:16 skrev Claudiu Popa <pcmantic...@gmail.com>: > > On Thu, Oct 22, 2015 at 8:03 PM, Peter Bittner <peter.bitt...@gmx.net> > wrote: > > Strictly speaking, Prospector isn't an alternative to flake8, but to > PyLint. The verbosity of PyLint with default settings is the main > critique of Prospector's author. He's running a nice service, by the > way, Landscape. Very nice and free for Open Source projects. > https://landscape.io/ > > > You do realize that Prospector is using Pylint as its underlying > technology? Can't really consider it an alternative in this case: > http://prospector.readthedocs.org/en/master/ > > > > _______________________________________________ > code-quality mailing list > code-quality@python.org > https://mail.python.org/mailman/listinfo/code-quality > _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
