Skip to content

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

Closed
@DonJayamanne

Description

@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.

Metadata

Metadata

Assignees

Labels

area-environmentsFeatures relating to handling interpreter environmentsauthor-verification-requestedIssues potentially verifiable by issue authorfeature-requestRequest for new features or functionalityneeds PRReady to be worked onverification-neededVerification of issue is requestedverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions