Turn back on cwd when venv is activated by the extension

[realratchet]

Hello,

I've been using ~6 month old vscode (1.76.2) until recently recently, when decided to update it to 1.81.1 (because 1.82 has broken sourcemap reloading) and noticed that python extension has started hiding CWD in the terminal when it activates it. I've tried looking any references to it in json/discussion/tickets but any keywords I could think off of didn't find anything useful.

Here's an example of no venv activated

Here's an example when venv is activated manually

Here's an example when venv is activated by the extension

Is there a way to disable it, I've been using this for 3 days now and I'm at my breaking point to where I permanently switch to 1.76.2. I can't seem to find any user config that disables this behaviour. I know that it shows the current directory near the terminal icon but it's way out of place because you actually have to move your focus and even then it doesn't show full path if you're dealing with directory tree that has directories with same name.

Thanks.

[brettcannon]

We don't specifically remove the current working directory from your prompt, we just (try) to add in the name of the virtual environment automatically. What's probably happening is the way we are doing this is breaking with your setup and causing the current working directory part of your prompt to be stripped out.

Turning this into a bug report.

[brettcannon]

#22150