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 pipenv environments are autoselected #23115

Closed
3 of 4 tasks
karrtikr opened this issue Mar 22, 2024 · 3 comments
Closed
3 of 4 tasks

Test pipenv environments are autoselected #23115

karrtikr opened this issue Mar 22, 2024 · 3 comments
Labels
testplan-item Test plan item/assignments for upcoming release
Milestone

Comments

@karrtikr
Copy link

karrtikr commented Mar 22, 2024

Refs: #19153

Complexity: 3

Create Issue


Requirements

  • Python extension pre-release

Verification

  • Install pipenv if not already https://pipenv.pypa.io/en/latest/#install-pipenv-today
  • Create 3 empty projects
  • Open each project in terminal and run the following command, record the python printed at end of it somewhere:
    pipenv run python -c"import sys;print(sys.executable)"
    
    image
  • For each project:
    • Open the project as a workspace folder in VS Code and create a new Python file
    • Make sure the recorded python is the one which is selected:
      image
@karrtikr karrtikr added the testplan-item Test plan item/assignments for upcoming release label Mar 22, 2024
@github-actions github-actions bot added this to the March 2024 milestone Mar 25, 2024
@ulugbekna
Copy link

Auto-selection worked with the first pipenv environment but in 2nd and 3rd environments it kept auto-selecting the first one:

image image

@Yoyokrazy
Copy link

First run through I created a .py file and my global python was selected. Deleted the file, reloaded the window, and re-tried and it worked. Worked through the second and third projects as well.

@karrtikr
Copy link
Author

karrtikr commented Mar 27, 2024

Thanks both for letting us know about this, I was able to diagnose the cause of the issue. It should be solved with #23139.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
testplan-item Test plan item/assignments for upcoming release
Projects
None yet
Development

No branches or pull requests

8 participants