25👍
sudo is unnecessary when creating a virtualenv and when installing with pip inside a virtualenv. Try the following instead:
$ virtualenv -p /usr/bin/python3.4 venv
$ source venv/bin/activate
(At this point, you can check that your virtualenv is active and using python 3.4 with which python, which should print something like /home/user/projects/venv/bin/python, and python --version, which should print Python 3.4.x)
$ pip install https://www.djangoproject.com/download/1.7b1/tarball/
2👍
I think the problem is sudo. The point of virtualenv is that you should not have to run anything as root — virtualenv will set up an environment in which you can install packages as a user. I imagine the issue is either that pip is assuming your use of sudo suggests that you want to install the package in the system package directory… or else that sudo itself is overriding the virtualenv changes to your environment in favor of root’s default environment.
Create a new virtualenv without sudo. Then activate it and run pip install without sudo.
- Returning a value with psycopg2
- Reordering fields in Django model
- What is the right way to use django-allauth with tastypie?
- How to measure the time profile of each django test?
0👍
try following
virtualenv --no-site-packages --distribute -p /usr/bin/python3 ~/.virtualenvs/py3
workon py3
pip install Django==1.7.4
- What is the correct way to deal with DB migration while using South, Django and Git?
- Form validation in django
- Saving Base64ImageField Type using Django Rest saves it as Raw image. How do I convert it to a normal image