🔒 miniconda vsc terminal relative path environment

[solar kelp]

I use miniconda as a package manager and I have several environments. Before how it used to work was that I can type conda to use miniconda commands no matter which environment was activated.

However, something happened recently that I cannot remember which makes it so that any miniconda environment activated within the Python interpreter causes the conda command to not work as well as the relative path to display not the project name.

For example, in this first image here is how it is normally. ~/Documents/Scripts, Programs, & Code/zzz_Other/Test Environments shown and is correct, and I can use conda on my default Python 3.11.6.

In this second picture, these are my available miniconda environments I can switch to in the interpreter.

When I switch to any environment, I get this error on my current terminal in this third picture.

And in this 4th picture, this is what happens when I type conda. It doesn't recognize the command but says it's a directory, even though it's in the PATH env variable. Also, the relative path displays as C:/Users/Abacus Paradox/AppData/Local/Programs/Microsoft VS Code and not the current project directory. But when I do ls it shows the files in my current project directory, so that confuses me.

This 5th picture shows that miniconda is in the PATH.

So, yeah I'm really at a loss as to what is happening. I don't know why my visual studio code terminal cares what the interpreter environment is because conda activate ENV is used for terminal related stuff like conda install or pip install. Also, I use git bash and it has always worked for miniconda and python.

[digital tide]

@solar kelp

Python help channel opened

Remember to:

• Ask your Python question, not if you can ask or if there's an expert who can help.
• Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
• Explain what you expect to happen and what actually happens.

:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.

Closes after a period of inactivity, or when you send !close.

[severe grove]

hard to tell what exactly is going wrong, but guessing some things that might solve common problems:

Double check that your PATHs are pointing to the most generic things possible, not specific installations/versions/environments

if you manually edited PATH, restart VSCode

use the commands

• Python Select Interpreter
• Python Clear cache and Reload Window
  then delete your existing terminals and create new ones

...also why git bash? If you want to use Linux, I'd recommend using WLS (Windows Linux Subsystem) and Dev Containers, but if you have no real reason to, it might be better to just use cmd.exe or powershell

[digital tide]

Python help channel closed

This help channel has been closed and it's no longer possible to send messages here. If your question wasn't answered, feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.