Using Pip to install packages to Anaconda Environment
<p>conda 4.2.13
MacOSX 10.12.1</p>

<p>I am trying to install packages from <code>pip</code> to a fresh environment (virtual) created using anaconda.  <a href="http://conda.pydata.org/docs/using/pkgs.html#install-non-conda-packages" rel="noreferrer">In the Anaconda docs</a> it says this is perfectly fine.  It is done the same way as for virtualenv.  </p>

<blockquote>
  <p>Activate the environment where you want to put the program, then pip install a program...</p>
</blockquote>

<p>I created an empty environment in Ananconda like this:</p>

<pre><code>conda create -n shrink_venv
</code></pre>

<p>Activate it:</p>

<pre><code>source activate shrink_venv
</code></pre>

<p>I then can see in the terminal that I am working in my env <code>(shrink_venv)</code>.  Problem is coming up, when I try to install a package using <code>pip</code>:</p>

<pre><code>(shrink_venv): pip install Pillow

Requirement already satisfied (use --upgrade to upgrade): Pillow in /Library/Python/2.7/site-packages
</code></pre>

<p>So I can see it thinks the requirement is satisfied from the system-wide package.  So it seems the environment is not working correctly, definitely not like it said in the docs.  Am I doing something wrong here?</p>

<p>Just a note, I know you can use <code>conda install</code> for the packages, but I have had an issue with Pillow from anaconda, so I wanted to get it from <code>pip</code>, and since the docs say that is fine.</p>

<p>Output of <code>which -a pip</code>:</p>

<pre><code>/usr/local/bin/pip
/Users/my_user/anaconda/bin/pip
</code></pre>

<p>** UPDATE **
I see this is pretty common issue. What I have found is that the conda env doesn't play well with the PYTHONPATH. The system seems to always look in the PYTHONPATH locations even when you're using a conda environment. Now, I always run <code>unset PYTHONPATH</code> when using a conda environment, and it works much better. I'm on a mac.</p>