[conda] conda update conda

[Mike Hagerty]

Can someone please explain how conda is meant to update itself ?
If I follow the instructions, I end up in a circle where "conda update
conda"
tells me to run "conda update conda" (see below).
I'm running on mac osx.

My understanding is that there should be just 1 conda executable in the
('base env') dir:
/usr/local/anaconda/bin/conda

and from all environments, a softlink is made in the env bin:
/usr/local/anaconda/envs/python3/bin/conda@ -> /usr/local/anaconda/bin/conda

And this is independent of whether an env is running python2.7 or python 3
(?)

I wonder if things are going wonky because I originally installed conda
using the
anaconda installer for python2.7 and later created an env for python 3 (?)

ie., If your base conda is python2.7, can you manage python3.x envs from
here,
or do you need to reinstall with a python3.x base and then create python2.7
envs ?
ie, is it backward compatible ?

***@Mikes-MBP> conda list conda
# packages in environment at /usr/local/anaconda:
#
# Name Version Build Channel
anaconda 2.0.1 np18py27_0 <unknown>
conda 4.5.3 py27_0 conda-forge
conda-build 3.10.2 py27_0 conda-forge
conda-env 2.6.0 0
conda-forge
conda-verify 2.0.0 py27_0 conda-forge


-------------------------------------------------------------------------
The Conda Ouroboros:

(base) ***@Mikes-MBP > conda update -n base conda
Solving environment: done


==> WARNING: A newer version of conda exists. <==
current version: 4.5.3
latest version: 4.5.4

Please update conda by running

$ conda update -n base conda

# All requested packages already installed.

conda -V

conda 4.5.3

conda search conda

...
conda 4.5.3 py36_0 conda-forge
conda 4.5.3 py36_0 pkgs/main
conda 4.5.4 py27_0 pkgs/main
conda 4.5.4 py35_0 pkgs/main
conda 4.5.4 py36_0 pkgs/main