On Mon, Jan 28, 2013 at 3:54 PM, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote: > We regularly hear complaints about the default settings file. I've noticed > the following patterns: > > 1) Beginners > a) Frustration. They skim the comments, tweak the settings and it doesn't > work as expected. The comments are fairly detailed, but they don't provide > context like the docs. > b) Confusion. There's too much information at once. "What am I supposed to > configure? Is STATICFILES_FINDERS important?" > > 2) Experienced users > a) Boredom. "Why do I have to make the same changes in every new project to > enable the admin?" > b) Doubt. "Is using STATICFILES_DIRS the current best practice? It's in the > default settings file."
I can confirm both of these patterns, especially 1a -- settings.py tends to be really overwhelming when I teach Django to new users. The first time we make a new app in my classes it can take like 5-10 minutes for everyone to figure out how to add it to INSTALLED_APPS. > - In general, do you think this is a good idea? Or am I misguided? I think it's a great idea -- +1. > - In detail, are there commits in the branch that seem wrong with regard to > the current best practices? I don't claim to know them all. I'll bet if *I* wrote this patch I'd do it slightly differently, but I don't see anything that's not more a matter of taste than anything technical. I don't want to contribute to any bikeshedding; this is good enough for me. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
