Python environments returned by the API is different from list in Interpreter Picker

[DonJayamanne]

• 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)

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.

[karrtikr]

This is expected as the API does not take a resource parameter for discovery, and extensions are expected to filter environments themselves. See workspaceFolder property under environment type to filter.

[DonJayamanne]

and extensions are expected to filter environments themselves

I didn't expect this change, this is a big change from the previous API

[karrtikr]

We can reconsider adding some sort of filtering back if that's the feedback from Jupyter. Can discuss with team tomorrow.

[DonJayamanne]

Never mind, I'll make the change at my end

[karrtikr]

We can add some default filtering without changing the API: microsoft/vscode-jupyter#11779 (comment).