re: Conda & Dealing with Conflicting Python(s) in your system VIEW POST

re: I am using miniconda, so I am unsure if the commands are different. I am able to add that line, and then use commands like conda activate, etc. but...

sorry my bad!

  • Miniconda is just a smaller version of Conda including just the bare minimum, such as the conda command

From what I can understand from what you said, I think you may have forgotten to add the symlink folder to the path!

So yes, scratch that thing that I told you in my previous comment (we were checking if conda was there).

Now, add this to the bashrc file (it always remains persistent to your last save and this file is run everytime you open a terminal) export PATH="/home/your-username/.symlinks:$PATH", and run source ~/.bashrc just to make sure that the path variable is updated (it's like re-running a script). Retry and let me know.

(you're on linux/unix right? I cannot help with Windows :))

Yeah I am running Ubuntu 16.04. So I did that and still same issue. I attached a picture. The only way to get it back to the miniconda location is to run unset PYTHONPATH and then when I run anything in a conda env, it finds the right path by itself.

Yes I am on Linux (specifically Ubuntu 16.04). I have added it to path and still getting the same error where the command doesn't register. Do you know any other common bugs it could be?

For now, I'm thinking to just add a question in the bashrc asking if I will be using conda during this session, and have that set the python path every time.

code of conduct - report abuse