 <p>I had this happen to me. Did you change your project path? </p> <p>When I first created the virtual environment, I used <code>~/src/my_project/venv</code> but later changed it to <code>~/projects/my_project/venv</code>. When I ran the activate scripts, it was using the old path. To fix this, I did a substitution on all of the scripts in the activate directory with the new path and <code>python</code>, <code>pip</code>, etc. were now sourced from the virtual environment.</p>