#12821 closed (wontfix)
Application settings
Reported by: | sorl | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | 1.1 |
Severity: | Keywords: | settings | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Providing application default settings is quite painful but still very common. I propose in similarity how the admin.py files can be located using autodiscover to have a settings file in the application directory which if located, values will be added to the settings object. Here is some code that I am using personally, it tries to import settings.py file in the app dir and there is no way to stop that, which i suggest must be optional, what do you think?
Attachments (1)
Change History (4)
by , 15 years ago
Attachment: | __init__.py added |
---|
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I started writing a similar patch tonight before I stumbled across this.
Settings in general needs some work, and you can follow where the discussion is going here: http://groups.google.com/group/django-developers/browse_thread/thread/c89e028a536514d3/7a80b7fada8e2c4b?lnk=gst&q=settings.py#7a80b7fada8e2c4b