Initialize conda with incorrect address

[peanutsugarlove]

During the process of starting the terminal

(base) PS E:\BaiduSyncdisk\python\openwebui> (& E:\Anaconda\Library\shell\condabin\conda-hook.ps1) ;
  (conda activate base)
&: The term 'E:\Anaconda\Library\shell\condabin\conda-hook.ps1' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
(base) PS E:\BaiduSyncdisk\python\openwebui> conda env list

The correct path should be E: \ Anaconda \ shell \ bondabin \ bonda-hook.ps1
But Conda mistakenly generated E: \ Anaconda \ Library \ shell \ bondabin \ bonda-hook.ps1
So it caused the terminal to be unable to initialize conda, which resulted in the inability to switch environments. After a day, it was discovered that it was a problem with this extension

[eleanorjboyd]

Sorry this happened and we are working on a fix. Can you retry it on the most recent pre-release version of the Python Environments extension? I merged in this change which was supposed to help with this: 4b7c3ac

[yayoinoyume]

I have a solution.
I am using a Windows computer with PowerShell 7. I temporarily fixed this incorrect location issue by adding redirect command parameters in the profile.

---

#region vscode python
#version: 0.2.0

if (($env:TERM_PROGRAM -eq 'vscode') -and ($null -ne $env:VSCODE_PWSH_ACTIVATE)) {

# 1. Fix VS Code wrong conda-hook path
$env:VSCODE_PWSH_ACTIVATE = $env:VSCODE_PWSH_ACTIVATE `
    -replace '(?i)Library\\shell\\condabin', 'shell\condabin'

# 2. activate env
try {
    Invoke-Expression $env:VSCODE_PWSH_ACTIVATE
} catch {
    Write-Error "Failed to activate Python environment: $_" -ErrorAction Continue
}

}
#endregion vscode python

---

[eleanorjboyd]

This is connected to a larger problem we were having with Conda activation which I did a rewrite of to fit with our new architecture but use prioritization like that for the old method. Can you try it again and let me know the status and the logs now that the improved version is out?

If you install the new pre-release of the python-environments extension and reload your window, you will have the new code. From there give it a try and if it doesn’t work, here are the steps to get me the necessary information for me to fix it. I have added extensive logging to hopefully make it easier:

1. use developer: set log level command to set your log level to trace
2. reload your window
3. copy all the logs out of your python-environments extension output channel. (if you do not feel comfortable posting this I can share my email so you can reach out to me specifically or you can sanitize your logs)
4. include what you expect to happen- so I can see where it went down the wrong path.

Again, thank you so much and I hope the rewrite will be a step up from the previous implementation. Thank you

[yayoinoyume]

I tried the preview version, and the path to "conda-hook.ps1" is correct this time, but even when I selected shell startup, an external cmd window still pops up when activating the virtual environment.

I have now reverted to the old version, and I'm still using the method of replacing the path as I mentioned earlier to solve the problem.

[eleanorjboyd]

glad to hear the conda hook path is correct and sorry you are still seeing the popup- linking to this issue I created to collect all the reports related to the cmd window popup: #712

[eleanorjboyd]

peanutsugarlove let me know if this fixes it for you, otherwise follow along to the issue I tagged for the cmd window popup issue resolution

[github-actions]

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.

Happy Coding!