Opened 14 years ago
Closed 13 years ago
#126 closed enhancement (fixed)
Don't import the settings module directly
| Reported by: | adehnert | Owned by: | |
|---|---|---|---|
| Priority: | trivial | Milestone: | Sometime |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Size: | tiny |
Description
Currently, we just do an "import settings" to access our configuration. We're supposed to use the settings object from django.conf instead (see https://docs.djangoproject.com/en/dev/topics/settings/#using-settings-in-python-code).
Change History (1)
comment:1 Changed 13 years ago by adehnert
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Fixed in commit afc53488a6bff4145f723bc1b6749e6bcba071bf:
Author: Alex Dehnert <adehnert@mit.edu> Date: Fri Feb 8 04:44:17 2013 -0500 Import settings from django.conf (ASA-#126) For some reason, importing the settings module directly is discouraged, and you should instead use the settings object from django.conf (see https://docs.djangoproject.com/en/dev/topics/settings/#using-settings-in-python-code).