[Answer]-No modules named core.management

by

1👍

Try to use pip instead of easy install. Every virtualenv has it installed by default (along with setuptools, which contain easy_install) and it is the recommended way of installing packages inside virtualenvs.

racech@CONFIG0001:~$ sudo apt-get install python-virtualenv
[...]
racech@CONFIG0001:~$ virtualenv test
New python executable in test/bin/python
Installing distribute.....done.
Installing pip...............done.
racech@CONFIG0001:~$ source test/bin/activate
(test)racech@CONFIG0001:~$ pip install django
[...]
Successfully installed django
Cleaning up...
(test)racech@CONFIG0001:~$ django-admin.py startproject testproject
(test)racech@CONFIG0001:~$ cd testproject/
(test)racech@CONFIG0001:~/testproject$ python manage.py runserver
Validating models...

0 errors found
February 20, 2014 - 10:12:51
Django version 1.6.2, using settings 'testproject.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

And as for the explanation it looks like easy_install installed Django not into your virtualenv, but to your system Python. You can check that by creating a new virtualenv with a different version of Python. Make a Virtualenv with undefault Python binary (3.x if you use 2.x and 2.x if you use 3.x as default) by running

virtualenv --python=/usr/bin/python3.2 myvirtualenv

and then check it by

python --version
sudo python --version

they should be different. Virtualenv replaces default Python environment only for the user which activated it. Therefore easy_install must have used system Python instead of virtualenv. Maybe you did run it with sudo as well?

👤Krzysztof Bujniewicz

Leave a comment