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

Sudden deactivate when 'Run-in-Terminal' #50

Open
anthonykim1 opened this issue Dec 3, 2024 · 0 comments · May be fixed by #108
Open

Sudden deactivate when 'Run-in-Terminal' #50

anthonykim1 opened this issue Dec 3, 2024 · 0 comments · May be fixed by #108
Assignees
@karthiknadig @anthonykim1
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone
January 2025

Comments

@anthonykim1
Copy link

Testing #24503

Aside from activate, deactivate buttons being on wrong state, when I have some terminal with zsh activated with (.venv) and I press on Run Python File, I get creation of a brand new terminal with 'deactivate' command before the execution of my Python file.
Not too sure if this is expected

Image
Image
@anthonykim1 anthonykim1 added the bug Issue identified by VS Code Team member as probable bug label Dec 3, 2024
@anthonykim1 anthonykim1 self-assigned this Dec 3, 2024
@karthiknadig karthiknadig transferred this issue from microsoft/vscode-python Dec 4, 2024
@karthiknadig karthiknadig added this to the January 2025 milestone Dec 16, 2024
@karthiknadig karthiknadig linked a pull request Jan 9, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karthiknadig karthiknadig

@anthonykim1 anthonykim1

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

Successfully merging a pull request may close this issue.

Better handling for venv activations karthiknadig/vscode-python-environments
2 participants
@karthiknadig @anthonykim1