Dne Wed, 2 Jul 2014 21:17:52 +0200 Aymeric Augustin <aymeric.augus...@polytechnique.org> napsal(a):
> 2014-07-02 17:21 GMT+02:00 Tomas Ehrlich <tomas.ehrl...@gmail.com>: > > > I'm just a bit confused with final decision. > > > > I don't think we have a decision yet ;-) Tim Graham made comment on PR: "Closing for now as the consensus seems to be adding a setting on the AppConfig is the correct approach." > > > > As Jannis commented on ticket: "This is simple, don't add a global setting > > but a parameter to the staticfiles app config. That's where such things > > belong now." > > > > That comment must have been written while I was working on app-loading and > its final scope wasn't known yet. > > I think a global setting isn't very different from a setting stored on the > app config. The app config provides a bit of namespacing, but a prefix such > as STATICFILES_ works just as well. > > At this time, we don't handle settings for contrib apps in their app config > classes. So if we want to handle this with a setting, it should be a global > setting. If we don't, my explanations are irrelevant. > I would really like to see app configs with app-specific settings. Personally, I don't like flat settings where namespaces are created with prefixes (eg. STATICFILES_ ). The idea of overriding class attributes in AppConfig seems promising. Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20140702221427.66f0bb8a%40bodhi. For more options, visit https://groups.google.com/d/optout.
