After siteprefs is finished loading the overrides, it could populate any missing values in django.conf.settings. Ideally it populates them with proxies clearly identified as duplicates of the overrides, so that they are not accidentally used again if reloading foo.settings.
This also helps with interoperability with other tools, such as
django-extensions cmd print_settings , which looks only in django.conf.settings
django-settings-context-processor is nice and simple, and fairly secure, but it doesnt work with siteprefs because it only looks in django.conf.settings
https://github.com/idlesign/django-siteprefs/issues/16 looks to support third-party apps. The easiest group is those which read from
django.conf.settings
.After siteprefs is finished loading the overrides, it could populate any missing values in
django.conf.settings
. Ideally it populates them with proxies clearly identified as duplicates of the overrides, so that they are not accidentally used again if reloadingfoo.settings
.This also helps with interoperability with other tools, such as
print_settings
, which looks only in django.conf.settings