What's the difference between `from django.conf import settings` and `import settings` in a Django project

Question:

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?

Asked By: tzenderman

||

Answers:

from django.conf import settings is better option.

I use different settings files for the same django project (one for “live”, one for “dev”), the first one will select the one being executed.

Answered By: mansuetus

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.

Answered By: juliocesar
Categories: questions Tags: , ,
Answers are sorted by their score. The answer accepted by the question owner as the best is marked with
at the top-right corner.