venv appears reactivated even though it isn't

[sgjohnson1981]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.85.2
• OS Version: Windows 10.0.19045

Steps to Reproduce:

1. Have an activated python virtual environment created by venv in a cmd terminal.
2. Restart the terminal (I had one of those warnings that it needed to be restarted).
3. When the terminal restarts, the venv appears as though it's still activated (its name is in the parentheses before the working directory).
4. Attempt to deactivate just using deactivate command.
5. Receive a deprecation warning from conda stating to use "conda deactivate" instead, even though it's not a conda environment.
6. Run echo %PATH% to see that order isn't correct for a venv environment.
7. Reactivate environment.
8. Run echo %PATH% again to see the directories in the correct order.
9. Realize it must not have actually been activated.

My guess is this has to do with VS Code attempting to "restore terminal history." I think a user would expect either the environment to be reactivated or it to not appear as though it's reactivated.

[karrtikr]

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority. Thanks for understanding and the patience!

[karrtikr]

Please provide the debug logs which can help diagnose the issue:

• Run Developer: Set log level command
• Select Trace
• Run Developer: Reload Window command
• Provide the output:

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

[karrtikr]

A lot of these issues were recently fixed, try the latest pre-release and stable version of the Python extension.

[sgjohnson1981]

It seems the terminal history feature has been completely eliminated, even though it seems it still says "History restored." Not only is the venv name gone when I restart VS Code the working directory is also reset to my home directory. So what history is restored? It's definitely not the command history, which to be honest, would be a nice feature as well. (Btw, I didn't switch to pre-release python version.) @karrtikr

[sgjohnson1981]

I switched to Pre-Release. Seems to be working as far as I can tell. Not sure why no history at all was restored on that first restart.

[sgjohnson1981]

Nevermind. Seems to be doing it again.

[karrtikr]

Hi, I've prepared an extension VSIX containing potential fix: https://github.com/microsoft/vscode-python/actions/runs/7853829284/artifacts/1235350371, please give it a try. You can install the VSIX using Extension: Install from VSIX command.

If it doesn't work, please provide the debug logs which can help diagnose the issue:

• Run Developer: Set log level command
• Select Trace
• Run Developer: Reload Window command
• Provide the output:

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

[sgjohnson1981]

Seems to be working now. Using 'where python' in the terminal has directories in the correct order.