Opened 17 years ago
Closed 17 years ago
#7015 closed (wontfix)
[PATCH] Per-project overrideable application specific settings
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | How to create a pull request | ||
Description ¶
It is often useful for an application to define its own settings that are then overrideable on a per-project basis. This is a patch derived from a method that I've been using in my apps for some time. The app skeleton path adds a file app_settings.py which contains a LocalApplicationSettings class. Its attributes define settings for the application. These settings can be overridden in settings.py with a predictable rubric: if the application is named 'foo' and the settings is BAR_SETTING, then by setting FOO_BAR_SETTING in settings.py it is overridden for that project.
Change History (2)
by , 17 years ago
| Attachment: | appsettings.patch added |
|---|
comment:1 by , 17 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Duplicate of #5049