Reputation: 1804

Django - "no module named django.core.management"

I get the following error when trying to run Django from the command line.

File manage.py, line 8, in <module>
     from django.core.management import execute_from_command_line
ImportError: No module named django.core.management

Any ideas on how to solve this?

Upvotes: 114

Answers (23)

Kalim Ullah

Reputation: 16

Run following command

python3 manage.py runserver

Instead of

python manage.py runserver

Upvotes: 0

Harun ERGUL

Reputation: 5942

The problem occurs when django isn't installed on your computer. You also get this error because the django.core.management module is missing.

To solve this issue we have to install django using pip. Open a command line prompt -> cmd(on windows) and enter the following command:

pip install django

This command will install django on your computer. So consider installing pip first. Here's how to install pip on a Windows machine

Upvotes: 6

Damini Suthar

Reputation: 1492

It is because of virtual enviornment configuration. You need to work on your virtual enviornmnet of Python. You should try on your command promt with,

workon virtual_enviornment_name

Upvotes: 0

user5683940

Reputation:

You can try it like so : python3 manage.py migrate (make sur to be in the src/ directory)

You can also try with pip install -r requirements.txt (make sur you see the requirements.txt file when you type ls after the migrate

If after all it still won't work try pip install django

Hope it helps

Upvotes: 1

Jek Hatulan

Reputation: 149

I experience the same thing and this is what I do.

First my installation of

pip install -r requirements.txt

is not on my active environment. So I did is activate my environment then run again the

pip install -r requirements.txt

Upvotes: 6

Rahul Satal

Reputation: 2237

I am having the same problem while running the command-

python manage.py startapp < app_name >

but problem with me is that i was running that command out of virtual environment.So just activate your virtual environment first and run the command again -

Upvotes: 7

Amir

Reputation: 8929

My case I used pyCharm 5 on mac. I also had this problem and after running this command my problem was solved

sudo pip install django --upgrade

Upvotes: 2

Syiwa Wahyu Saputra

Reputation: 121

You must choose your Project first before running the server , type this workon your_project_name then python manage.py runserver

Upvotes: 0

GoldFish

Reputation: 107

I had the same problem and following worked good, you should navigate main folder in your project than type:

source bin/activate

Upvotes: 2

user314165

Reputation: 21

I got the same problem trying to use the python manage.py runserver. In my case I just use sudo su. Use the terminal as a root and try it again an it works partially. So I use python manage.py migrate comand and it fix it.

Upvotes: 0

MAhsan

Reputation: 113

I had the same issue and the reason I was getting this message was because I was doing "manage.py runserver" whereas doing "python manage.py runserver" fixed it.

Upvotes: 2

Code Tree

Reputation: 2209

sudo pip install django --upgrade

did the trick for me.

Upvotes: 47

Hemanth Gowda

Reputation: 620

had the same problem.run command 'python manage.py migrate' as root. works fine with root access (sudo python manage.py migrate )

Upvotes: 1

user4055792

Reputation:

In my case, I am using Ubuntu. The problem can be that I don't have the permission to write to that folder as a normal user. You can simply add the sudo before your command and it should work perfectly. In my case sudo python manage.py syncdb.

Upvotes: 2

sk8asd123

Reputation: 1705

In case this is helpful to others... I had this issue because my virtualenv defaulted to python2.7 and I was calling Django using Python3 while using Ubuntu.

to check which python my virtualenv was using:

$ which python3
>> /usr/bin/python3

created new virtualenv with python3 specified (using virtualenv wrapper https://virtualenvwrapper.readthedocs.org/en/latest/):

$ mkvirtualenv --python=/usr/bin/python3 ENV_NAME

the python path should now point to the virtualenv python:

$ which python3
>> /home/user/.virtualenvs/ENV_NAME/bin/python3

Upvotes: 3

user1578297

Reputation: 159

well, I faced the same error today after installing virtualenv and django. For me it was that I had used sudo (sudo pip install django) for installing django, and I was trying to run the manage.py runserver without sudo. I just added sudo and it worked. :)

Upvotes: 14

Ashish

Reputation: 106

Okay so it goes like this:

You have created a virtual environment and django module belongs to that environment only.Since virtualenv isolates itself from everything else,hence you are seeing this.

go through this for further assistance:

http://www.swegler.com/becky/blog/2011/08/27/python-django-mysql-on-windows-7-part-i-getting-started/

1.You can switch to the directory where your virtual environment is stored and then run the django module.

2.Alternatively you can install django globally to your python->site-packages by either running pip or easy_install

Command using pip: pip install django

then do this:

import django print (django.get_version()) (depending on which version of python you use.This for python 3+ series)

and then you can run this: python manage.py runserver and check on your web browser by typing :localhost:8000 and you should see django powered page.

Hope this helps.

Upvotes: 4

Pete Varley

Reputation: 412

Are you using a Virtual Environment with Virtual Wrapper? Are you on a Mac?

If so try this:

Enter the following into your command line to start up the virtual environment and then work on it

1.)

source virtualenvwrapper.sh

source /usr/local/bin/virtualenvwrapper.sh

2.)

workon [environment name]

Note (from a newbie) - do not put brackets around your environment name

Upvotes: 10

mgPePe

Reputation: 5907

Most probably in your manage.py the first line starts with !/usr/bin/python which means you are using the system global python rather than the one in your virtual environment.

so replace

/usr/bin/python

with

~/projectpath/venv/bin/python

and you should be good.

Upvotes: 22

adamadam

Reputation: 48

This also happens if you change the directory structure of your python project (I did this, and then puzzled over the change in behavior). If you do so, you'll need to change a line in your /bin/activate file. So, say your project was at

/User/me/CodeProjects/coolApp/

and your activate file is at

/User/me/CodeProjects/coolApp/venv/bin/activate

when you set up your project, then you changed your project to

/User/me/CodeProjects/v1-coolApp/

or something. You would then need to open

/User/me/CodeProjects/v1-coolApp/venv/bin/activate

find the line where it says

VIRTUAL_ENV="/User/me/CodeProjects/coolApp"
export VIRTUAL_ENV

and change it to

VIRTUAL_ENV="/User/me/CodeProjects/v1-coolApp"

before reactivating

Upvotes: 2

Anagha

Reputation: 760

I got the same error and I fixed it in this manner:

I had to activate my virtual environment using the following command

source python2.7/bin/activate

Upvotes: 30

keesar

Reputation: 1

File and Directory ownership conflict will cause issues here. Make sure the ownership of the directories and files under the project are to the current user. (You can change them using the chown command with the -R option.) Try rerunning the command: this solved the problem for me when running through the "First Django App" sample:

python manage.py startapp polls

Upvotes: -1

RaviU

Reputation: 1213

It sounds like you do not have django installed. You should check the directory produced by this command:

python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"

To see if you have the django packages in there.

If there's no django folder inside of site-packages, then you do not have django installed (at least for that version of python).

It is possible you have more than one version of python installed and django is inside of another version. You can find out all the versions of python if you type python and then press TAB. Here are all the different python's I have.

$python
python            python2-config    python2.6         python2.7-config  pythonw2.5
python-config     python2.5         python2.6-config  pythonw           pythonw2.6
python2           python2.5-config  python2.7         pythonw2          pythonw2.7

You can do the above command for each version of python and look inside the site-packages directory of each to see if any of them have django installed. For example:

python2.5 -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"
python2.6 -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"

If you happen to find django inside of say python2.6, try your original command with

python2.6 manage.py ...

Upvotes: 58

Django - &quot;no module named django.core.management&quot;

Answers (23)

Related Questions

Django - "no module named django.core.management"