Code comment to ignore/disable/exclude warning about prospector HOT 7 CLOSED

The case I had, was that by default the secret key is in the Django settings and I'm perfectly happy with that:

foo.settings (foo/settings.py):
    L20:0 None: dodgy - secret
    Possible hardcoded secret key

from prospector.

At this point in time, dodgy is really super simple and has no mechanism for turning off errors - I will add one though!

from prospector.

Simple workaround for Django Secret Key:

# Prospector bypass
g = globals()
g["SECRET_KEY"] = 'my_secret'

from prospector.

I have similar issues with some of my code. For example, I have APIs that take a type=... keyword argument. Prospector keeps complaining that I'm overwriting the built-in type function.

However, the type argument is perfectly fine and much nicer than something like type_=... for consumers of this API. The "downside" is that the internal implementation has to be careful not to use the type() function (or access it through an alias), which is far better than forcing developers to use an ugly API.

from prospector.

With the 0.9 release, prospector now recognises "# noqa" comments and suppresses all warnings from all tools on those lines. The specific pylint disabling still works, too.

from prospector.

I'll leave this issue open however to remind me to document this properly!

from prospector.

Thanks, @carlio

from prospector.