-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Test language servers with Python 2.7 #17541
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
Comments
I do not have Python setup on my Linux, thus I have swapped platform assignments with @mjbvz . I hope that is fine. |
These were all pretty straight forward with no issues, let me know if you need any additional/thorough testing |
@isidorn if you need help setting Python up then please let me or anyone on the team know and we can help you out. |
@brettcannon thanks for the offer, I already have it setup on my Mac and works nicely. |
@mjbvz I took you off as I accidentally verified under Linux out of habit from launching VS Code under WSL. 😄 I also went ahead and verified under Windows as well. |
Uh oh!
There was an error while loading. Please reload this page.
Refs: #17225
Complexity: 3
Create Issue
Requirements
pyenv
on Mac/Linux, orpyenv-win
on Windows, and callpyenv install 2.7.16
virtualenv
with python 2.7:path/to/python2 -m pip install virtualenv
"python.experiments.optInto": ["All"],
in your user settings. If not, add it and reload VS Code.python.defaultInterpreterPath
entries in your user and workspace settings are at their default valuepython
python.insidersChannel
todaily
, wait for the download and installation to happen and reload VS Code)Scenario 1: Jedi
.vscode/settings.json
:/path/to/python2 -m virtualenv .venv
Editor support is inactive since language server is set to None.
is printed, and that language server capabilities are disabledScenario 2: Default
.vscode/settings.json
:/path/to/python2 -m virtualenv .venv
Starting Pylance language server.
is printed, and that language server capabilities are workingScenario 3: Pylance
.vscode/settings.json
:/path/to/python2 -m virtualenv .venv
Starting Pylance language server.
is printed, and that language server capabilities are workingThe text was updated successfully, but these errors were encountered: