Pylint doesn't point to virtualenv Python interpreter

I am fairly sure that you need to install Pylint under your virtual environment and then run that instance of it.

Make life easier:

I would suggest that anybody working a lot in virtual environments create a batch file, (in a known location or on the path), or Bash script with something like the following called something like getlint.bat:

pip install pylint

Invoking this after activating the virtual environment will install Pylint into that virtual environment. If you are likely to be offline or have a poor Internet connection you can, once when you have a good Internet connection, (possibly once for each of Python 2 and 3):

mkdir C:\Some\Directory\You\Will\Leave\Alone
pip download --dest=C:\Some\Directory\You\Will\Leave\Alone pylint

Which will download Pylint and its dependencies to C:\Some\Directory\You\Will\Leave\Alone, and you can modify getlint.bat to read:

pip install pylint --find-links=C:\Some\Directory\You\Will\Leave\Alone

It will then use the pre-downloaded versions.

Noufal Ibrahim's answer works if you execute Pylint manually.

If you execute Pylint from you editor/IDE, you need to configure the plugin correctly.

• vim/syntastic
• atom/linter-pylint
• ...

It can get tricky. This may be considered a bug of each IDE/plugin, but that's how it is.

Modifying /usr/bin/pylint to write #!/usr/bin/env python as suggested in another answer fixes this for every use of Pylint (manual use, or any editor integration).

However, at least in Debian, using #!/usr/bin/python is a design choice, not a bug. See here for the rationale.

To avoid modifying that system file, one can create a copy of /usr/bin/pylint in /usr/local/bin:

cp /usr/bin/pylint /usr/local/bin/pylint
vi usr/local/bin/pylint # Edit the file to use /usr/bin/env python

This won't be broken by a Pylint update, but still infringes Debian's "strongly preferred choice".

This method requires root privileges. An unprivileged user may create an alias

alias pylint='/usr/bin/env python $(which pylint)'.

I always develop in virtualenv and I set up a postmkvirtualenv hook to install Pylint and flake8 automatically when creating a virtualenv, so I don't use the versions distributed by Debian anymore.

I ran into this problem, too. My solution was simply to edit the Pylint program's shebang, like so... (your path to Pylint may be different than mine, though)

sudo vim /usr/bin/pylint

Replacing:

#!/usr/bin/python

With:

#!/usr/bin/env python

The issue has been solved in chat (link in comments).

The problem lay in using sudo yum install pylint, because it installed Pylint in the global environment. The solution was to use the following command:

pip install -i http://f.pypi.python.org/simple pylint

Note the -i usage as the regular index seemed to be broken for the asker.

If for some reason you need to keep Pylint in the global space instead of your virtual environment, you can use the recommendation in here: Pylint + VirtualEnv.

It basically says to configure your Pylint using the init-hook and encoding version of a Python program that will use the global Pylint and load the rest of the environment.

When you're using Pipenv / virtualenv, install Pylint inside the virtualenv:

pipenv install --dev pylint

Or, if you don't use Pipenv, install it with pip after you activated your virtualenv:

# Activate virtualenv, e.g., `. env/bin/activate`
pip install pylint

You can get there by calling the target Python interpreter:

./env/bin/python -m pylint ...

# Or in an already active environment
python -m pylint ...

For pylint installed globally, it can not recognize the packages installed inside the virtual environment, even if we are inside the virtual env. First, we can install pylint-venv in the global level (outside the virtual env):

pip install pylint-venv

Then inside the pyproject.toml file for this project, we can configure a init-hook for pylint:

[tool.pylint.main]
init-hook ="""
try:
  import pylint_venv
except ImportError:
  pass
else:
  pylint_venv.inithook()
"""

Tested on pylint 2.17, works well for me.

I'm using the Syntastic and Pylint combination, and since I have many different virtualenvs that I can work on at any given time, I've created a wrapper over the virtualenv command that, among some other things, installs Pylint after all the requirements.

That way, whenever I activate a virtualenv, I'll get its own Pylint version.

I ran into the same problem just today. Continuing on ThorSummoner's answer, when using Pylint with pylint-django inside of a virtual environment, such as Pipenv, make sure to call Pylint using the target python interpreter (python -m pylint).

It is a good approach, which will work locally and on your CI as well is to write-down the lint command in the script section of your Pipfile:

[scripts]
lint = "python -m pylint [--options] all-my-modules-names..."

Then calling Pylint is as easy as:

pipenv run lint