Closed
Description
- Install latest Jupyter pre-release extension
- Install latest Python pre-release extesnion
- Install VS Code insiders
- Open a workspace folder A
- Create a virtual env here named '.venvA'
- Go to interpreter picker and verify
.venvA
is displayed - Go to Jupyter Kernle picker and verify
.venvA
is displayed (jupyter will get this via the Python extension API)
- Open a different workspace folder B
- Go to interpreter picker and verify
.venvA
is not displayed - Go to Jupyter Kernle picker and verify
.venvA
is displayed (jupyter will get this via the Python extension API)
- Go to interpreter picker and verify
The problem is, the kernel picker now displays python environments that belong to other workspace folders.
This is inconsistent with the interpreter picker in the Python extension.
Users will as a result see lot more python environments in the kernel picker,
This is a change in the behaviour of the Python Extension API.