Environment activation is not working reliably with "Command Prompt"

[bersbersbers]

I think this picture says it all:

Open a terminal, start typing, terminal auto activation interferes.

My settings (clean profile):

{
    "terminal.integrated.defaultProfile.windows": "Command Prompt",
    "python.useEnvironmentsExtension": true,
}

What is so frustrating about this issue is that this has been working fine for a long time (I opted into the pythonTerminalEnvVarActivation experiment) until about a year ago. Then the experiment was discontinued, the functionality was moved to a different extension, but - sorry to say it so bluntly - from a user POV, nothing has improved since then.

[karthiknadig]

@bersbersbers Please try setting python-envs.terminal.autoActivationType to shellStartup. That is the equivalent of the experiment you are talking about.

Notes on this:
For most cases this works with Shell Integration feature in VS Code. If SI is off or a terminal does not support SI then we update shell startup script to activate environments only when opened in VS Code. In case, shell does not support dynamic evals like nu it will fall back to command activation.