You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to install the dev requirements using pip install, I run into the following error:
$ pip install -r requirements-dev.txt
Collecting pytest==2.5.1 (from -r requirements-dev.txt (line 5))
Collecting py==1.4.19 (from -r requirements-dev.txt (line 6))
Collecting mock==1.0.1 (from -r requirements-dev.txt (line 7))
Collecting flake8==2.1.0 (from -r requirements-dev.txt (line 10))
Collecting mccabe==0.2.1 (from -r requirements-dev.txt (line 11))
Collecting pep8==1.4.6 (from -r requirements-dev.txt (line 12))
Collecting pyflakes==0.7.3 (from -r requirements-dev.txt (line 13))
Collecting Sphinx==1.2 (from -r requirements-dev.txt (line 16))
Using cached Sphinx-1.2-py33-none-any.whl
Collecting docutils==0.11 (from -r requirements-dev.txt (line 17))
Collecting Jinja2==2.7.1 (from -r requirements-dev.txt (line 18))
Collecting MarkupSafe==0.18 (from -r requirements-dev.txt (line 19))
Collecting Pygments==1.6 (from -r requirements-dev.txt (line 20))
Collecting Paver==1.2.1 (from -r requirements-dev.txt (line 23))
Using cached Paver-1.2.1.tar.gz
Could not import setuptools which is required to install from a source distribution.
Traceback (most recent call last):
File "/Users/stew/.envs/rummage/lib/python3.5/site-packages/pip/req/req_install.py", line 387, in setup_py
import setuptools # noqa
File "/Users/stew/.envs/rummage/lib/python3.5/site-packages/setuptools/__init__.py", line 10, in <module>
from six.moves import filter, map
ImportError: No module named 'six'
This is fixed by changing the Paver version in requirements-dev.txt from 1.2.1 to the current 1.2.4. It's possible I'm doing something wrong--I'm not clear on why this was happening in the first place--but this change resolves the issue. I'm happy to provide further context if you tell me what info would be helpful.
It looks like the requirements-dev.txt on the master branch is 3 years old--should it be updated? I'll make a pull request so you can update it easily if you think it should be.
The text was updated successfully, but these errors were encountered:
When trying to install the dev requirements using
pip install
, I run into the following error:This is fixed by changing the Paver version in
requirements-dev.txt
from 1.2.1 to the current 1.2.4. It's possible I'm doing something wrong--I'm not clear on why this was happening in the first place--but this change resolves the issue. I'm happy to provide further context if you tell me what info would be helpful.It looks like the
requirements-dev.txt
on the master branch is 3 years old--should it be updated? I'll make a pull request so you can update it easily if you think it should be.The text was updated successfully, but these errors were encountered: