This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Geetings! How did you upgrade conda? 4.4.7 is really quite old at this point, and I would suggest getting the latest from here: https://docs.conda.io/en/latest/miniconda.html Most notably, I believe they have drastically improved the install procedure so that running: conda init From the shell should help set things up. Ryan > Hi Ryan, > > I have upgraded to version 4.4.7 but am getting an issue with my path > variable. I have attempted to do what it recommends to no avail. This is > strange since I had no issues with python when going through the metpy > Monday series a few years ago. > > bash-3.2$ conda env list > > # conda environments: > > # > > base * /Users/mhaworth/miniconda3 > > metpy /Users/mhaworth/miniconda3/envs/metpy > > playground /Users/mhaworth/miniconda3/envs/playground > > unidata-workshop /Users/mhaworth/miniconda3/envs/unidata-workshop > > /opt/miniconda3 > > > bash-3.2$ conda activate metpy > > > CommandNotFoundError: Your shell has not been properly configured to use > 'conda activate'. > > If your shell is Bash or a Bourne variant, enable conda for the current > user with Ticket Details =================== Ticket ID: WNC-125958 Department: Support Python Priority: Low Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.