title: ImportError: No module named urllib3 when installing pip
body: <p>I have an issue with virtualenvwrapper that requires reinstalling pip as the first step, and I am getting a strange complaint about urllib3:</p>
  
  <pre><code>$ python get-pip.py 
  Traceback (most recent call last):
    File "get-pip.py", line 19177, in &lt;module&gt;
      main()
    File "get-pip.py", line 194, in main
      bootstrap(tmpdir=tmpdir)
    File "get-pip.py", line 82, in bootstrap
      import pip
    File "/tmp/tmppQTQty/pip.zip/pip/__init__.py", line 16, in &lt;module&gt;
    File "/tmp/tmppQTQty/pip.zip/pip/vcs/mercurial.py", line 9, in &lt;module&gt;
    File "/tmp/tmppQTQty/pip.zip/pip/download.py", line 39, in &lt;module&gt;
    File "/tmp/tmppQTQty/pip.zip/pip/_vendor/requests/__init__.py", line 61, in &lt;module&gt;
    File "/tmp/tmppQTQty/pip.zip/pip/_vendor/requests/packages/__init__.py", line 29, in &lt;module&gt;
  ImportError: No module named urllib3
  </code></pre>
  
  <p>when I search the pip file <code>get-pip.py</code>, I don't see any reference to urllib3. </p>
  
  <p>I have python2.6, py2.7, and py3.4 on the machine</p>
  
  <pre><code>cchilders:~/Downloads 
  $ which python
  /usr/local/bin/python
  
  cchilders:~/Downloads 
  $ which pip
  /usr/local/bin/pip
  
  
  cchilders:/usr/local/bin 
  $ ls
  2to3           easy_install-2.7  ipython   pip3              smtpd.py
  celery         fop               ipython2  pip3.5            uncompyle2
  celerybeat     grunt             jsonlint  pydoc             virtualenv
  celeryd        idle              pbr       python            virtualenv-clone
  celeryd-multi  ipdb              pip       python2.6         virtualenvwrapper_lazy.sh
  charm          iptest            pip2      python2.6-config  virtualenvwrapper.sh
  easy_install   iptest2           pip2.7    python-config
  </code></pre>
  
  <p>Python is defaulting to 2.6.9 which isn't what I want:</p>
  
  <pre><code>cchilders:/usr/bin 
  $ python
  Python 2.6.9
  </code></pre>
  
  <p>I do not have anaconda on the machine, which caused someone else's problem. Any advice what to do now appreciated, thank you</p>