Show linter codes

[bmhkim]

I'd really like to see the linter code included with the linter message. An example use case involves working on a codebase that's not entirely PEP-8 compliant. (e.g. tabs instead of spaces) Display of the pylint code makes it easier to disable the message in the project's .pylintrc.

[posita]

Please include the human readable versions as well (e.g., undefined-variable is synonymous with E0602, etc.).

[bmhkim]

I've got a fix for this hacked together, and will submit a pull request.

[bmhkim]

@posita If you want this immediately, I have a fork that seems to be working for me: bmhkim/linter-pylint

[posita]

Nice! 👍

[SpainTrain]

👍

[SpainTrain]

This should be closed in the latest released version. @bmhkim mind confirming and closing if true?

[posita]

LGTM:

[SpainTrain]

@posita are those import errors true positives? There is an issue open for false positives on relative imports (#58).

Thanks for testing!

[posita]

@posita are those import errors true positives?

They are valid(ish). They are absolute imports provided via a virtualenv that Atom is not aware of, so I'm pretty sure they are not implicated by #58.

[SpainTrain]

Awesome, just wanted to make sure =-D

Thanks!