Sorry Carl, I agree with pretty much everything you said. I was talking a bit too abstract and I had misunderstood. I will concentrate on a few use cases:
with a app level settings.py file i didnt really refer to automatic import, as that can easily be done now. I had more like a admin.register in mind, like the appsettings app by jared. it would be nice if apps had an easy and constitent way of "registering" somehow: a) project settings (settings that affect the installation, etc... this can include automatic install of dependencies, etc... but normally do not change, this could be done in a similar script ) b) app settings (settings that change once and while, but that are meant to be changed by a superuser, or admin) c) user settings (settings that are to be set and changed by a user himself, that could be changed in a "profile app") more to come, now is food time -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
