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.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.