You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have limited support for language servers in a web environment: In-file intellisense should be available, but that should be it.
Requirements
Make sure you have the Pylance and Jupyter extensions installed
Use any stable Python 3 version
Use the latest pre-release version of the Python extension
Make sure your workspaces contain at least one Python file and one notebook
Scenario 1: Single-root workspace
Verify the following when opening a Python file in a single-root workspace:
Starting {Pylance/Jedi} language server for {workspace basename} should be printed in the Python output channel
The Python Language Server output channel should be available
Intellisense should work in a Python file
When switching language servers, no prompt to reload should appear, and a new Starting.... should appear
If switching to None, Editor support is inactive since language server is set to None for {workspace basename}. should appear in the Python output channel
Intellisense should still show something when changing Python interpreters
Intellisense should work in a Jupyter notebook
Scenario 2: Multi-root workspace
Note that Pylance has multiroot-workspace awareness while Jedi doesn't, so Intellisense results will differ depending on which language server you use.
Verify the following when opening Python files in a multi-root workspace:
If using Jedi, there should be as many Starting Jedi language server for {workspace basename} printed in the Python output channel as there are workspace folders (might require opening a file in each folder)
If using Pylance, there should only be one Starting Pylance language server for {workspace basename} printed in the Python output channel
The Python Language Server output channel should be available
Intellisense should work
When switching language servers, no prompt to reload should appear, and new Starting.... lines should appear
If switching to None, Editor support is inactive since language server is set to None for {workspace basename}. should appear in the Python output channel only once
Intellisense should still show something when changing Python interpreters
Intellisense should work in a Jupyter notebook
Scenario 3: Pylance not installed
Uninstall Pylance
Make sure that the value for the user setting python.languageServer is Default or Pylance, and make sure that the test workspace has no value for the python.languageServer setting
Open a workspace with a Python file and open the Python file to trigger an extension load
Verify that a prompt appears with 3 options: Install Pylance, revert to Jedi, remind me later
Verify that selecting the "Revert to Jedi" option starts up the Jedi language server (check the line in the Python output channel, check that the Python Language Server output channel exists, check Intellisense)
Verify that selecting the "Remind me later" option dismisses the prompt and does not start up any language server
Verify that selecting the "Install Pylance" option takes you to the Pylance extension page, and that once you install Pylance the Pylance language server should be started (check the line in the Python output channel, check that the Python Language Server output channel exists, check Intellisense)
The text was updated successfully, but these errors were encountered:
Refs: #18509
Complexity: 4
Create Issue
Special consideration for web
We currently have limited support for language servers in a web environment: In-file intellisense should be available, but that should be it.
Requirements
Scenario 1: Single-root workspace
Verify the following when opening a Python file in a single-root workspace:
Starting {Pylance/Jedi} language server for {workspace basename}
should be printed in the Python output channelPython Language Server
output channel should be availableStarting....
should appearNone
,Editor support is inactive since language server is set to None for {workspace basename}.
should appear in the Python output channelScenario 2: Multi-root workspace
Note that Pylance has multiroot-workspace awareness while Jedi doesn't, so Intellisense results will differ depending on which language server you use.
Verify the following when opening Python files in a multi-root workspace:
Starting Jedi language server for {workspace basename}
printed in the Python output channel as there are workspace folders (might require opening a file in each folder)Starting Pylance language server for {workspace basename}
printed in the Python output channelPython Language Server
output channel should be availableStarting....
lines should appearNone
,Editor support is inactive since language server is set to None for {workspace basename}.
should appear in the Python output channel only onceScenario 3: Pylance not installed
python.languageServer
isDefault
orPylance
, and make sure that the test workspace has no value for thepython.languageServer
settingThe text was updated successfully, but these errors were encountered: