Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use pylint in vscode on Ubuntu #333

Closed
momoblydblk opened this issue Dec 2, 2017 · 6 comments
Closed

Unable to use pylint in vscode on Ubuntu #333

momoblydblk opened this issue Dec 2, 2017 · 6 comments
Labels
area-linting bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@momoblydblk
Copy link

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0 by Microsoft
Python Version: 3.5.3
OS and version: Ubuntu 16.04 LTS

Actual behavior

Still prompt for installing pylint after already installed.

Expected behavior

Pylint working well

Steps to reproduce:

  • I think it is just myself who has this problem.
@DonJayamanne
Copy link

installing pylint after already installed

  • What environment is pylint installed in?
  • What's the current interpreter selected in your vscode? (display at the bottom of the status bar).
  • Please type the following commands and provide the output for each:
which python 
python -m pylint --version

@DonJayamanne DonJayamanne added info-needed Issue requires more information from poster area-linting bug Issue identified by VS Code Team member as probable bug labels Dec 2, 2017
@DonJayamanne
Copy link

@momoblydblk have you got an update on the above information?

@momoblydblk
Copy link
Author

I got the update, but currently not able to do it. Need several hours to put my tasks down to handle this.
Thanks
Best
MomoBD

@momoblydblk
Copy link
Author

Main developing environment: Python 3.5
Python 3.5.3 (default, Jan 19 2017, 14:11:04) [GCC 6.3.0 20170118] on linux

which python3.5 output:
/usr/bin/python3.5

python -m pylint --version output:
No config file found, using default configuration __main__.py 1.7.4, astroid 1.5.3 Python 3.5.3 (default, Jan 19 2017, 14:11:04) [GCC 6.3.0 20170118]

@brettcannon brettcannon added awaiting 1-verification and removed info-needed Issue requires more information from poster labels Dec 11, 2017
@ericsnowcurrently ericsnowcurrently self-assigned this Jan 18, 2018
@ericsnowcurrently
Copy link
Member

Hi @momoblydblk! I haven't been able to reproduce the problem thus far. Keep in mind that pylint is installed per-interpreter. So if you are trying to use a different version of Python (or a differently installed interpreter) then you have to be sure pylint is installed in each.

Also, what is in your settings (both user settings and workspace settings). Look for the settings in the "python" namespace (start with "python.").

@ericsnowcurrently ericsnowcurrently added info-needed Issue requires more information from poster and removed awaiting 1-verification labels Jan 18, 2018
@ericsnowcurrently ericsnowcurrently removed their assignment Jan 18, 2018
@MikhailArkhipov
Copy link

In the upcoming release linters are installed per user which should further improve the case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-linting bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants