Undocumented dependency on new-ish pip #940
Description
As of now, anyone running "pip install --upgrade setuptools" on a CentOS 6 machine will find it fails horribly:
pip install --upgrade setuptools
Downloading/unpacking setuptools from https://pypi.python.org/packages/b1/d1/3df86b914d72b18d37266f964a11576f135eadbb7d2e3c5165377e4263bc/setuptools-34.0.1.zip#md5=9e907950a94d38c0295df0da2507c280
Downloading setuptools-34.0.1.zip (617kB): 617kB downloaded
Running setup.py egg_info for package setuptools
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "setuptools/__init__.py", line 10, in <module>
from six.moves import filter, map
ImportError: No module named six.moves
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "setuptools/__init__.py", line 10, in <module>
from six.moves import filter, map
ImportError: No module named six.moves
I discovered this when a long-functioning build script started failing all of a sudden.
I gather from #937 and #938 that a more recent pip is required, and indeed installing it with pip install --upgrade pip does allow installation of setuptools to proceed.
May I suggest that the README should specify what version of pip is required, as it is a newer version than is present on many systems.