title: Virtualenv uses wrong python, even though it is first in $PATH
body: <p>I had a problem where <code>python</code> was not finding modules installed by pip while in the virtualenv.</p>
  
  <p>I have narrowed it down, and found that when I call <code>python</code> when my virtualenv in activated, it still reaches out to <code>/usr/bin/python</code> instead of <code>/home/liam/dev/.virtualenvs/noots/bin/python</code>.</p>
  
  <p>When I use <code>which python</code> in the virtualenv I get:</p>
  
  <p><code>/home/liam/dev/.virtualenvs/noots/bin/python</code></p>
  
  <p>When I look up my <code>$PATH</code> variable in the virtualenv I get:</p>
  
  <p><code>bash: /home/liam/dev/.virtualenvs/noots/bin:/home/liam/bin:/home/liam/.local/bin:/home/liam/bin:/home/liam/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin: No such file or directory</code></p>
  
  <p>and yet when I actually run <code>python</code> it goes to <code>/usr/bin/python</code></p>
  
  <p>To make things more confusing to me, if I run <code>python3.5</code> it grabs python3.5 from the correct directory (i.e. <code>/home/liam/dev/.virtualenvs/noots/bin/python3.5</code>)</p>
  
  <p>I have not touched <code>/home/liam/dev/.virtualenvs/noots/bin/</code> in anyway. <code>python</code> and <code>python3.5</code> are still both linked to <code>python3</code> in that directory. Traversing to <code>/home/liam/dev/.virtualenvs/noots/bin/</code> and running <code>./python</code>, <code>./python3</code> or <code>./python3.5</code> all work normally.</p>
  
  <p>I am using <code>virtualenvwrapper</code> if that makes a difference, however the problem seemed to occur recently, long after install <code>virtualenv</code> and <code>virtualenvwrapper</code></p>