Even though the original question seems to be from 2015, this 'bug' seems to affect users installing pip-10.0.0 as well.
The workaround is not to modify pip, however to change the way pip is called. Instead of calling /usr/bin/pip call pip via Python itself. For example, instead of the below:
pip install <package>
If from Python version 2 (or default Python binary is called python) do :
python -m pip install <package>
or if from Python version 3:
python3 -m pip install <package>