Test: Try out the Environments extension

[karthiknadig]

Refs: #24025, #24067, #23155

• anyOS @anthonykim1
• anyOS @eleanorjboyd
• anyOS @aeschli

Complexity: 3

Create Issue

---

Introduction

You are testing the environments extension. This extension is intended to replace the functionality of the python extension, specifically the environment management parts. When installed along side with Python extension, the environments extension will provide the various features that you normally used the python extension for, such as selecting environments, creating, deleting, managing packages etc. The current implement supports virtual environment via venv as a built-in feature.

Requirements:

1. Download and install the following, pick the platform specific VSIX from the build artifacts:
   • Envs extension: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=308165&view=artifacts&pathAsName=false&type=publishedArtifacts
   • Python extension: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=307999&view=artifacts&pathAsName=false&type=publishedArtifacts
2. Reload VS Code

Testing:

1. Open a python workspace
2. Create a venv environment if it does not exist. If it does make sure that it got selected. This view should have the info you need:
   
3. Try running python in the terminal using the run-in-terminal command from the editor run menu
4. Try switching environments, see if it is using the right one when you run. Ensure status bar shows the change.
5. Since venv are activated environments, environments view and project view should have an inline command create terminal try it.
6. Try deleting the .venv you created from file explorer, see what happens. (Note: deleting from outside of VS Code might not work because VS Code watcher does not report folder deletions, unless we specifically watch that folder)

[eleanorjboyd]

seems like a env can have multiple versions of wheel?

should we signal which is being used actively?