Unsolved #11638

[ArenaGrenade]

#11638 has been closed with @karrtikr specifying that this issue will be fixed, its 2024 now and I am facing the exact same issue in VS Code on Windows. Powershell doesn't automatically activate the current conda environment.

I have Conda on path and the shell is properly initialized along with conda being initialized in the shell. So, after VS Code opens the terminal, I hit "conda activate env", it activates the env.

What I want is for VSCode to automatically run activate the directory specific environment like it does with command prompt.

Env Activation settings are correct, powershell runs with execution policy bypass.

Is there anything I can do to fix this? I can't even modify the powershell command to run conda activate before providing me access, because as far as I am aware, settings.json doesnt have access to current directory - unless I create a version of it for every project I have and manually set python path and so on. This is practically infeasible.

[karthiknadig]

@ArenaGrenade Would it be possible to share a screen recording of the issue? Also can you share the logs, I am interested in the initial part of the logs where it prints out which experiments you are in.

We have an experiment where the activation happens in the background so your powershell will have the right environment variables but the prompt may not show that it is in an environment.