Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation Error #1

Open
larue3000 opened this issue Feb 5, 2016 · 1 comment
Open

Installation Error #1

larue3000 opened this issue Feb 5, 2016 · 1 comment

Comments

@larue3000
Copy link

Recently watched Building theatlantic.com homepage’s WYSIWYG admin with Django and Knockout

I could the repo and ran ./setup.sh. However, setup fails with the following:

Installing collected packages: setuptools, six, wheel, django, django-grappelli, django-ckeditor, django-select2-forms, django-nested-admin, django-generic-plus, django-curation, Pillow, pytz, python-xmp-toolkit, django-cropduster, lxml, defusedxml, futures, django-pipeline, libsass, django-appconf, rcssmin, rjsmin, django-compressor, django-libsass
Running setup.py develop for django
Complete output from command /Users/tt/development/django-ko-demo/bin/python -c "import setuptools, tokenize; file='/Users/tt/development/django-ko-demo/src/django/setup.py'; exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" develop --no-deps --home=/var/folders/qk/5fllnslx74qdf791fm854llc0000gn/T/tmpMZsK6n:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help

error: option --home not recognized

Any insight with resolving this would be appreciated.

@fdintino
Copy link
Member

fdintino commented Feb 5, 2016

I hope you enjoyed the talk!

I'm sorry to say that I'm unable to duplicate this error. Searching around for that error message turns up people having issues running pip install with the -e (i.e. --editable) at the same time as -t (or --target). It doesn't look like it from what you've pasted, but is there any chance you passed arguments to ./setup.sh, for instance ./setup.sh -t?

The only other thing I can think of is if you have a private pypi server specified in your ~/.pypirc file that has different versions of the packages in requirements.

If neither of those is the case, try changing line 42 of setup.sh:

"$CURR_DIR/bin/easy_install" "pip==6.1.1"

to

"$CURR_DIR/bin/easy_install" pip

so that it uses the very latest version of pip. Hopefully something above will help you set it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants