Fix Python – What’s the difference between `from django.conf import settings` and `import settings` in a Django project

Question

Asked By – tzenderman

I’m reading up that most people do from django.conf import settings but I don’t undertstand the difference to simply doing import settings in a django project file. Can anyone explain the difference?

Now we will see solution for issue: What’s the difference between `from django.conf import settings` and `import settings` in a Django project


Answer

import settings will import the first python module named settings.py found in sys.path. Usually (in default django setups) it allows access only to your site defined settings file, which overwrites django default settings (django.conf.global_settings).

So, if you try to access a valid django setting not specified in your settings file you will get an error.

django.conf.settings is not a file but an object (see source) making an abstraction of the concepts, default settings and your site-specific settings. Django also does other checks when you use from django.conf import settings.

You can also find it in the django docs.

Hope this helps.

This question is answered By – juliocesar

This answer is collected from stackoverflow and reviewed by FixPython community admins, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0