title: Yet another `bash: pip: command not found`
body: <p>Lots of installation instructions tell you to do <code>pip install [package]</code>. But in my case that won't work, it'll say <code>-bash: pip: command not found</code>  </p>
  
  <p><code>python pip install [package]</code> works OK. Likewise for <code>easy_install</code>, won't run by itself, will run when started with python. </p>
  
  <p>I'm confused as to how it <em>should</em> work. Pip is no executable, there's no module called pip.py, there's only <code>&lt;path&gt;\pip\__init__.py</code>. So if <code>pip install [package]</code> is to work properly, the bash shell must understand when to act as a python interpreter. Which it doesn't. </p>
  
  <p>I don't believe all those install instructions are off. So I must be missing something. What?</p>
  
  <p><a href="https://stackoverflow.com/questions/9780717/bash-pip-command-not-found">This</a> didn't help, nor did <a href="https://stackoverflow.com/a/30017353/1016065">this</a>, in fact trying <code>sudo apt-get install python-pip</code> led to what I think is an <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787165;msg=5" rel="nofollow noreferrer">unresolved bug</a>. So I had to revert to <a href="https://stackoverflow.com/a/40578125/1016065">this solution</a>, to get me a somewhat working pip. (Now read again from the top). </p>
  
  <p><strong>Edit</strong>: Python 2.7. Not 3.x.  </p>