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.

Sign up for GitHub

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

Jump to bottom

selecting "set as workspace env" doesn't work #55

Open
eleanorjboyd opened this issue Dec 3, 2024 · 1 comment
Open

selecting "set as workspace env" doesn't work #55

eleanorjboyd opened this issue Dec 3, 2024 · 1 comment
Assignees
@karthiknadig
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone
January 2025

Comments

@eleanorjboyd
Copy link
Member

eleanorjboyd commented Dec 3, 2024 •
edited by karthiknadig
Loading

Testing #24503

  1. attempt to select a global env as the workspace env
  2. 🐛 nothing happens, a new terminal still activates the old selected .venv
  3. did check and the interpreter used (like the one in the bottom bar) is correct so it is getting set for the workspace but not selected for the terminal?

Image

global-no-update.mov
@karthiknadig karthiknadig transferred this issue from microsoft/vscode-python Dec 4, 2024
@karthiknadig
Copy link
Member

karthiknadig commented Dec 5, 2024 •
edited
Loading

@eleanorjboyd Can you repro this if you have python extension activate features disabled?
Image

@karthiknadig karthiknadig added this to the January 2025 milestone Dec 16, 2024
@karthiknadig karthiknadig added the bug Issue identified by VS Code Team member as probable bug label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karthiknadig karthiknadig

Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
January 2025
Development

No branches or pull requests
2 participants
@karthiknadig @eleanorjboyd