3 ms·

It seems you're looking for tools to manage code quality. In that case I highly recommend prospector (http://prospector.landscape.io/en/master/ http://prospecto

It seems you're looking for tools to manage code quality. In that case I highly recommend prospector (http://prospector.landscape.io/en/master/ http://prospector.landscape.io/en/master/). It wraps a whole bunch of tools in one interface. I suggest paying close attention to any code that scores high on McCabe code complexity.

StavrosK 10y ago
Prospector looks great, thanks for the tip! One problem I always have with these tools is that even one false positive is enough to stop me from using it. On a tool that's used for pass/fail, even one false positive means it's useless because I can never make it pass. For example, it's throwing a "dodgy" warning on my Django project because of the SECRET_KEY variable in settings.py.
- shuzchen 10y ago
  By no means should you just use prospector as is. The defaults are pretty good, but if you have a huge project it'll make more sense to do a little configuration, and most of the tools that prospector wraps are configurable. I for one don't use the default lint configuration. I like dodgy and I actually pull out my secret key from settings.py (I pull it from the system environment). Otherwise you can just disable dodgy by using a custom profile (http://prospector.landscape.io/en/master/profiles.html#enabling-and-disabling-tools http://prospector.landscape.io/en/master/profiles.html#enabl...)
  - StavrosK 10y ago
    I'll look into it, but my settings file always has a fake secret key in it (that will be overridden on production) to cut down on the amount of configuration needed for new dev setups. I'll look into configuring it, but having to # noqa a bunch of lines isn't ideal :-/ Hopefully it won't get to that.
nthompson 10y ago
Just found and fixed multiple bugs using prospector; even better it flagged some code as suspicious that I was previously unwilling to touch because I couldn't understand it.

StavrosK 10y ago

Prospector looks great, thanks for the tip! One problem I always have with these tools is that even one false positive is enough to stop me from using it. On a tool that's used for pass/fail, even one false positive means it's useless because I can never make it pass. For example, it's throwing a "dodgy" warning on my Django project because of the SECRET_KEY variable in settings.py.

shuzchen 10y ago
By no means should you just use prospector as is. The defaults are pretty good, but if you have a huge project it'll make more sense to do a little configuration, and most of the tools that prospector wraps are configurable. I for one don't use the default lint configuration. I like dodgy and I actually pull out my secret key from settings.py (I pull it from the system environment). Otherwise you can just disable dodgy by using a custom profile (http://prospector.landscape.io/en/master/profiles.html#enabling-and-disabling-tools http://prospector.landscape.io/en/master/profiles.html#enabl...)
- StavrosK 10y ago
  I'll look into it, but my settings file always has a fake secret key in it (that will be overridden on production) to cut down on the amount of configuration needed for new dev setups. I'll look into configuring it, but having to # noqa a bunch of lines isn't ideal :-/ Hopefully it won't get to that.

nthompson 10y ago

Just found and fixed multiple bugs using prospector; even better it flagged some code as suspicious that I was previously unwilling to touch because I couldn't understand it.