Setting to show (venv) in terminal anyways

[a-Datana]

i think the title is pretty self explanatory.

since the last vscode update vs code hides the (venv) or (virual enviroment name here) text in the terminal, which is a small thing but still brought up issues cause trusting it does sometimes mean installing packages globally.
which is suboptimal.

i'd like an option which shows that indicator again.

[nickdalts]

This was driving me crazy

[austinwitherspoon]

This is also beneficial if you have multiple virtual environments, since it used to show the name of the virtual environment you were actively in (if they have different names), and remind you if you needed to close that terminal and reopen.

[bigalnz]

+1 - removing that is not a helpful feature.

[karrtikr]

Hi all, please note the inability to show (venv) is a limitation rather than a feature, of the new way of activating environments via environment variables. If you click "Learn more", it should have more details: link.

The limitation comes from VS Code and Powershell itself, as none of them provide us with an environment variable that we can set to change the terminal prompt.

Interested folks can try using "Command prompt" shell instead, use Select default profile to change the shell, which should have the (venv).

[bigalnz]

What about git bash on Windows? Can it work in there?

…

On Tue, 20 Feb 2024, 20:47 Kartik Raj, ***@***.***> wrote: Hi all, please note the inability to show (venv) is a limitation rather than a feature, of the new way of activating environments via environment variables. If you click "Learn more", it should have more details: link <https://github.com/microsoft/vscode-python/wiki/Activate-Environments-in-Terminal-Using-Environment-Variables> . The limitation comes from VS Code and Powershell itself, as none of them provide us with an environment variable that we can set to change the terminal prompt. Interested folks can try using "Command prompt" shell instead, use Select default profile to change the shell, which should have the "venv". — Reply to this email directly, view it on GitHub <#22917 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSLKREC6AOW2SMJBM7T6OTYURIIVAVCNFSM6AAAAABDJ3MS7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGY2DIOJTGA> . You are receiving this because you commented.Message ID: ***@***.***>

[karrtikr]

@bigalnz Git bash is not supported by the Python extension currently.

[bigalnz]

So this auto activation of the terminal is a feature of the Python plugin - not native VSCode?

[bigalnz]

A question on So here may also be worth voting for to get coverage on this question : https://stackoverflow.com/questions/78005138/make-venv-default-terminal-for-project-in-vscode/78030464#78030464

[karrtikr]

I'm changing this to a feature request, and if it gets enough upvotes, maybe VS Code can consider us giving us such a feature: #22917 (comment).

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[kyrlon]

So this auto activation of the terminal is a feature of the Python plugin - not native VSCode?

Issue #23008 has gifs showing an old extension version activating all 3 on windows 10

[kyrlon]

This is also beneficial if you have multiple virtual environments, since it used to show the name of the virtual environment you were actively in (if they have different names), and remind you if you needed to close that terminal and reopen.

I often use the python launcher py and if the terminal is not actively stating its virtual environemnt , my modules are installed global instead unfortunately.

[martinandrovich]

I was looking for this because my Git Bash terminal was not sourcing my Python venv (and the text didn't show even though it was sourced). For anyone else looking, the fix was to add this to .bashrc:

[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"

read more about it here and here.

[brettcannon]

I'm going to close this in favour of #22611 which would bring back the old solution as at least an option. You can also opt out of the experiment if you want.