Skip to content

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

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

Closed
ulugbekna opened this issue Mar 25, 2024 · 2 comments
Assignees
Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@ulugbekna
Copy link

Testing #23115

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

image image
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Mar 25, 2024
@karrtikr
Copy link

Thanks for letting us know about this. Closing in favor of #23115 (comment).

Currently pipenv discovery isn't triggered automatically when a new workspace is opened, because it is considered a "global" locator, so it requires a refresh of interpreters to take place before autoselection can happen.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Mar 27, 2024
@github-actions github-actions bot added the info-needed Issue requires more information from poster label Mar 27, 2024
@karrtikr
Copy link

It should also 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
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

2 participants