Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test support for detection and selection of conda environments lacking a python interpreter #18731

Closed
2 tasks done
karrtikr opened this issue Mar 21, 2022 · 0 comments
Closed
2 tasks done

Comments

@karrtikr
Copy link

karrtikr commented Mar 21, 2022

Refs: #18357

Complexity: 4

Create Issue


Requirements

  • Make sure Conda is installed. Tagging everyone on the team as we already have a bunch of environments available, and it may take a significant time for other folks to install stuff.
  • Use pre release build of the python extension.

Step 1: Test discovery

  1. Activate Python extension
  2. Create two conda environments like so:
conda create -n test1
conda create -n test2
  1. Refresh the interpreter's list using the refresh icon to see the environment:
    image

Step 2: Test selection

  1. Select the environment via the interpreters list.
  2. Notice status bar displays the following:
    image
  3. Expand the notification and click on the hyperlink, the output channel should open which describes the commands extension is running:
    image
  4. Note environment should still be usable while installation is ongoing, play around with it. Try debugging a simple python file for example:
print("Hello world!")

Packages like ipykernel should also be installable at this point.

  1. Notice status bar indicates that a interpreter refresh is triggered once installation has finished.
  2. Once refresh has finished, notice interpreter list now indicates that Python is installed within the environment:

6. Double check the output channel to make sure there aren't any unexpected errors.
@karrtikr karrtikr added triage-needed Needs assignment to the proper sub-team testplan-item labels Mar 21, 2022
@karrtikr karrtikr added this to the March 2022 milestone Mar 21, 2022
@karrtikr karrtikr removed the triage-needed Needs assignment to the proper sub-team label Mar 21, 2022
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Mar 21, 2022
@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Mar 21, 2022
@karrtikr karrtikr added triage-needed Needs assignment to the proper sub-team and removed triage-needed Needs assignment to the proper sub-team labels Mar 21, 2022
@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Mar 21, 2022
@ghost ghost assigned karthiknadig and rchiodo Mar 22, 2022
@rchiodo rchiodo removed their assignment Mar 22, 2022
@karthiknadig karthiknadig removed their assignment Mar 22, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants