Clean up module level settings

[mwarkentin]

Brought up by @kezabelle in #12:

The side-effect of doing it this way (and I'm guilty of it myself; a lot) is that it is cached at the module-level. It mostly isn't a problem for the app as-is because the biggest use-case it may break is override_settings, which isn't being used.

There was a ticket about documenting a specific way, but no resolution came of it.

[mwarkentin]

• http://stackoverflow.com/questions/11238514/why-is-djangos-settings-object-a-lazyobject
• https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/#use-of-django-conf-settings

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.