title: How to set up Anaconda so that it doesn't affect other environments like 'homebrew python pip' and Pyenv on MacOS?
body: <p>It is well known that Anaconda installation on macOS can cause trouble with other widely used package/environment managers like Homebrew, Pyenv, Virtualenv, etc.</p>
  
  <p>The majority of the solutions I've found are 'Anaconda-centric', i.e. using Anaconda as the main python manager and setup <code>conda env</code> for homebrew etc.</p>
  
  <p>However, I am looking for a solution that's kind of 'Homebrew-centric', and setup Anaconda as a compliment. Anaconda should be set up in a way that when ever <code>conda</code> is used, it will work with its own Python, own packages. And leave the rest of system untouched. </p>
  
  <p>The motivation for such solution is because that, for example, when one's main work-flow use homebrew Python3 (<code>python3</code>), homebrew pip (<code>pip3</code>) and Pyenv (<code>pyenv</code>) with <code>requirement.txt</code>. And occasionally using Anaconda when a project is required.</p>