a) is probably what i would personally leave in settings.py, or in a conf/settings.py MEDIA_URL, projectname, etc...
a bit behind on a project, ill take a look at appsettings this weekend :) On Mar 7, 12:03 am, Jared Forsyth <jabap...@gmail.com> wrote: > It seems like the best place for "project settings"(a) would be applicable > is through some ./manage.py command, perhaps "installapps" or something > along those lines. This would probably be the place to do database > modifications between versions. > (b) could be served by a "readonly" flag in the settings (if you were using > appsettings) > and (c) is provided by appsettings out of the box. > So it looks like the thing that needs work/thought/design decisions would be > (a). Could you give an example use case of that sort of "project > installation setting"? > > Jared > > > > On Sat, Mar 6, 2010 at 5:56 AM, stuff4ash <ashwo...@gmail.com> wrote: > > 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<django-developers%2Bunsubscr > > i...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-developers?hl=en. -- 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.
