Pylint in Sublime Text 2

Question

So, I have been using Sublime for a while as a simple text editor, but I dare to ground plugins to work, and I am faced with the problem of getting pylint to work. In particular, I installed it and the Sublime package manager works for me, but I'm not sure how to include paths in my sublime settings.

I did not find very useful documentation on this, but if you want to point me to this, this will be a perfectly acceptable answer. My main problem is that currently every time I save the file, the following error message appears:

"Please define the full path to 'lint.py' in the settings"

I understand this error message, which is great, I just have no idea where the sublime settings or the standard format for determining the path. Any help would be appreciated.

Answer 1

The SublimeLinter GitHub page has pretty comprehensive instructions that should describe how to set everything up. Briefly go to Preferences->Package Settings->SublimeLinter->Settings - Default to find out where the various parameters are defined. Then open Preferences->Package Settings->SublimeLinter->Settings - User to change something, since the main settings will be overwritten when the package is updated. Remember that the settings files are in JSON format, so you need to open and close the curly braces to enclose the settings in them, and a comma between them:

 { "sublimelinter_delay": 30, "sublimelinter_mark_style": "none" } 

I didn’t get your error, are you sure you are using a regular SublimeLinter and not a new beta? I just installed it on my working machine (I used it for a while at home), and after restarting ST2 it works like a charm with Python.

Answer 2

I had the same problem. I found this comes from the "Pylinter" package. I removed Pylinter and added SublimeLinter, it covers more than python and is well used. I enjoy it quite a bit.

Answer 3

From the command line, simply run:

 sudo easy_install pylint sudo easy_install pep8 

After that, restart your sublime.

Answer 4

Today I face the same situation. In my case, this is because I have not installed pylint on my system yet. It works fine after I installed pylint via pip. Just for other people.