-
Notifications
You must be signed in to change notification settings - Fork 336
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugnotebook-intellisenseIntellisense & other language features in notebook cells for any languageIntellisense & other language features in notebook cells for any languageverifiedVerification succeededVerification succeeded
Milestone
Description
Environment data
- VS Code version: 1.57.1
- Jupyter Extension version (available under the Extensions sidebar): v2021.6.999406279
- Python Extension version (available under the Extensions sidebar): v2021.6.944021595
- OS (Windows | Mac | Linux distro) and version: Windows 19043
- Python and/or Anaconda version: 3.8.5
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
- Jupyter server running: Local
Expected behaviour
Upon changing the kernel in the top right Pylance should detect module changes and resolve imports
Actual behaviour
Pylance will only detect kernel changes if you change the interpreter via the command palette
Before changing via command palette
Imports resolve
Steps to reproduce:
- Create a venv and install any pip module foo
- Create a notebook and import foo
- The pylance import detection will not update via changing kernel
- Changing via
Python: Select Interpreter
in the command palette will update Pylance
Note: code execution will work as if the venv is selected, but highlighting doesn't.
Another note: I'm sure a lot of my lingo I'm using is incorrect, I'm just starting out :)
ChristophSchranz and RiverMint78
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugnotebook-intellisenseIntellisense & other language features in notebook cells for any languageIntellisense & other language features in notebook cells for any languageverifiedVerification succeededVerification succeeded