Claude proposed a PR which simply adds the setting as an AppConfig attribute: https://github.com/django/django/pull/6460
Feedback would be welcome as to whether this seems sufficient or if we need something more complex. I imagine this pattern will become fairly common if we decide to move in this direction. On Thursday, July 3, 2014 at 10:47:16 AM UTC-4, Andre Terra wrote: > > > On Thu, Jul 3, 2014 at 3:12 AM, Aymeric Augustin < > [email protected] <javascript:>> wrote: > >> My concern -- and the reason why I started talking about an API -- is, >> if every app clutters the AppConfig namespace with arbitrary names, >> improvements to AppConfig may create name clashes. >> > > Hence my suggestion of encapsulating all those different "settings" in > AppConfig.settings. > > Cheers, > AT > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e36b821f-e9d7-44cd-aaa6-2d09597448f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
