0👍
I have just noticed that I did have a wrong version of python on the second machine – debian does not have python2.7, installing 2.7 and pip for is the solution
2👍
If you are just copying the virtualenv to the second machine you may encounter some issues. From the virtualenv site:
Normally environments are tied to a specific path. That means that you
cannot move an environment around or copy it to another computer. You
can fix up an environment to make it relocatable with the command:
$ virtualenv --relocatable ENV
This will make some of the files
created by setuptools or distribute use relative paths, and will
change all the scripts to use activate_this.py instead of using the
location of the Python interpreter to select the environment.Note: you must run this after you’ve installed any packages into the
environment. If you make an environment relocatable, then install a
new package, you must run virtualenv –relocatable again.
- [Answered ]-Replace get_context_data with get_object in Django 1.5
- [Answered ]-Cleaning up after a python script has been run locally vs from Django
- [Answered ]-Rabbitmq token based authentication
- [Answered ]-Django primary key does not exist