Inconsistent handling of settings
Currently we use settings (and their defaults) a bit inconsistently.
For example DEFAULT_REPLY_TO_EMAIL
can be accessed directly (settings.DEFAULT_REPLY_TO_EMAIL
) or indirectly (from core.notifications import DEFAULT_REPLY_TO_EMAIL
). The latter falls back to a sane default. The former may return None
.
Since Django does not seem to support partial defaults (see Django and custom defaults), we will need to do this on our own.
Should we move all defaults to stadt.common_settings
? Or is there another way?