False positive E0213 no-self-argument for decorator which extends staticmethod about pylint HOT 7 CLOSED

Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):

we need (much) deeper understanding of decorators in astroid for this.

in the mean time a custom transform should do the trick (requires forthcoming transformation API).

from pylint.

Original comment by BitBucket: mitar, GitHub: @mitar?:

So in current stable version this is not possible to achieve? Is there some other way?

from pylint.

Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):

the release should come until the end of july. The easiest you can do remains to disable this false positive manually using inline # pylint: disable pragma.

from pylint.

Original comment by BitBucket: mitar, GitHub: @mitar?:

I already have custom checkers so there is no problem adding more. :-) If there is/will be a way. :-)

from pylint.

Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):

in this case you'll have to use astroid (former astng) API to detect usage of your decorator and then hack the underlying function node arguments.

You may want to take a look at pylint/astroid tip, read astroid/doc/extending.rst and some code, then try and ask questions on python-projects or code-quality mailing list (doc is rather rough but that would be a good occasion to enhance it)

from pylint.

Original comment by BitBucket: mitar, GitHub: @mitar?:

I survived until now with reading existing checkers and object introspection. :-)

But yes, a good idea. I could just override values and set name of decorator to "staticmethod".

from pylint.

Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore):

Solved with https://bitbucket.org/logilab/astroid/commits/05d0fbdee9d6d26e024cfe9ea32d18e543373321 in astroid. Now pylint has a basic understanding of decorator chaining and tries to infer what those decorators return, but again, it's not exhaustive.

from pylint.