[Answered ]-Django virtual environment disaster

I assume you’re using virtualenv. If so, do you know where it put the bin directory? If so, run source bin/activate. After that, when you try runserver, it should use the correct Python instance.

More complete:
source /path/to/bin/activate

But I typically run source bin/activate from the directory that contains the related bin.

I found pew to be a very handy tool for managing your virtualenvs. Once its installed, basically, you can just do pew new env_name then pew workon env_name to activate an environment.

One of my colleagues use it on Mac OS X without issues.