Pylint message template overridden by linter

[AWPelican]

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0
Python Version: 3.6.3
OS and version: Fedora 26

Actual behavior

I was trying to set the --msg-template argument in python.linting.pylintArgs, but found that there were, surprisingly, no changes in the VS Code linter pop-ups or console output.

Oluwafemi Sule pointed out in his answer to my StackOverflow question that the message template is actually hardcoded into the linter for Pylint.

Expected behavior

I would have expected that passing in a --msg-template argument would have allowed me to change the format of the Pylint messages in the linter.

As a side note, it appears the Pylint project favors using the message symbol (e.g. 'trailing-whitespace') over the message msg_id (e.g. 'C0303') that is currently used in Visual Studio Code, per the examples in its documentation its default message template since pylint 1.0, and this FAQ answer.

[brettcannon]

I believe we control --msg-template so we can read the output from Pylint itself, otherwise we can't parse the response to use the results.

[DonJayamanne]

We could improve the linter message to include the message symbol (e.g. 'trailing-whitespace')

[AWPelican]

That sounds good to me. My main interest here was just that--to allow a quick way to see the human-readable message symbol.

[brettcannon]

I think it's a reasonable idea to include the human-readable message since Pylint has been slowly shifting that way itself.

[jcdyer]

I've got a PR for this up at #495.

[brettcannon]

To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.