I have hit a bit of a brick wall regarding the set up of django 1.7 using a virtualenv configured to Python 3.4.
I have created a Python 3.4 virtualenv using:
sudo virtualenv --no-site-packages -p /usr/bin/python3.4 venv
I have then activated the env using:
source venv/bin/activate
Once in the activated virtualenv i have tried:
sudo pip install https://www.djangoproject.com/download/1.7b1/tarball/
This installs django in the Python 2.7 directory and not in the virtual environment..
Checking with pip freeze
shows no installed packages
I have tried downloading the zip for django 1.7 and using python setup.py install
within the environment but still get the install occurring outside of the env and in the 2.7 directory..
Any advice or pointers on what i'm doing wrong would be really appreciated!!
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/