Can choose decorators that mutate a function's signature

[AWhetter]

Description

This adds a new option function_mutators that allows too-many-function-args, unexpected-keyword-arg, and no-value-for-parameter to not get raised for functions that are decorated with a decorator mentioned in function_mutators.

I figured it would be too difficult to try and infer what a decorator was doing so this seemed like the best solution, even though it means that there will be cases where a function is called with incorrect arguments will be missed by pylint when the function is decorated with a mutator decorator.

Type of Changes

	Type
✓	🐛 Bug fix
✓	✨ New feature
	🔨 Refactoring
	📜 Docs

Related Issue

Close #259

[coveralls]

Coverage increased (+0.002%) to 90.081% when pulling 3b1247f on fix_259 into 3dd27c9 on master.

[schrockn]

This is an awesome change and thanks for the hard work on this project! Would absolutely love it if this was incorporated into a new release. Looks like there hasn't been once since March?

[PCManticore]

Not yet @schrockn but the new release would happen very soon.

[iddan]

Any update regarding the release?

[muneebabbas93]

@PCManticore This very simple change would allow us to remove a bunch of # pylint: disable=no-value-for-parameter. Any chance of this getting a release in the 1.9 branch? :)

Serves us right for still using python 2 though :(

[beasteers]

this is great! Is there a way to define function_mutators using inline comments (e.g. # pylint: function_mutator)? It would be nice if we could avoid having to maintain a separate list that I'm inevitably going to forget to update.

[hippo91]

@beasteers it don't seem so. The only way seems to use the rcfile.