Hi all! Life with DJANGO_SETTINGS_MODULE has been great. However, it requires the settings to be an importable module. In most cases, this is a straight forward "simple" python script.
Sometimes it looks like it could make sense to add an environment variable that could use a file that is not importable as a python module, ie.: DJANGO_SETTINGS_FILE=/etc/yourapp/production.py DJANGO_SETTINGS_FILE=~/yourapp_production.py DJANGO_SETTINGS_FILE=settings.py # relative to pwd Then, in this file, we could override the default project settings there without having to put the new file in an importable module, ie. in /etc/yourapp/production.py: from yourapp.settings import * DATABASES=... CACHES=... SECRET_KEY=... I'm sure this has been discussed before but didn't find anything by searching DJANGO_SETTINGS_FILE in the ML. What's your opinion on this ? Is it time to upgrade this ? Best, -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op19-0JeL8Jdcq70-pvwz%2Bi2hfKtopEvihca_rGfH1DrPww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
