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

Add ability to change pylint's python interpreter when changing working interpreter #397

Closed
chaNcharge opened this issue Dec 11, 2017 · 1 comment
Labels
area-linting bug Issue identified by VS Code Team member as probable bug

Comments

@chaNcharge
Copy link

chaNcharge commented Dec 11, 2017

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0
Python Version: 3.6.3 and 2.7.14
OS and version: macOS 10.13.2

Feature request

I frequently work with two different python versions, python 2.7.14 and 3.6.3. I have pylint installed on both versions; however, when I switch interpreters from 2 to 3 (and vice versa), pylint is stuck on the python 2 interpreter, which was the version pylint was most recently installed. I know it's possible because I made a shell script in my system's path that can change pylint python interpreters once, but it'd be even better if it it works within VSCode.

Actual behavior

I have to change pylint python version manually by reinstalling it in the appropriate python version, or by uninstalling the one I'm not using.

Expected behavior

When I change python interpreters, pylint will also change to the respective python interpreter. Like running a command with python3 -m pylint ... or python2 -m pylint ...

@brettcannon brettcannon added awaiting 1-verification area-linting bug Issue identified by VS Code Team member as probable bug labels Dec 12, 2017
@brettcannon
Copy link
Member

Currently @DonJayamanne is working on refactoring our tool execution code so this should hopefully get fixed when that work completes. As of right now the issue is we are executing the pylint command which means you probably that command links to your Python 2 install.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
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
Projects
None yet
Development

No branches or pull requests

3 participants