I just pushed a patch based on this discussion: https://github.com/django/django/commit/2ff93e027c7b35378cc450a926bc2e4a446cacf0
On 22 janv. 2014, at 00:08, Russell Keith-Magee <russ...@keith-magee.com> wrote: > For my part, it's a light smell, in that it's a configuration variable that's > in a place you wouldn't historically expect to find a configuration variable, > for the purpose of defining a string substitution, which makes it mildly > implicit behavior. Based on explicit > implicit, I'd rather see users > actually type what they want to get (an AppConfig). This is tracked here: https://code.djangoproject.com/ticket/21822 -- Aymeric. -- 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/274F89A3-7100-4456-9B09-4C0F47D15B20%40polytechnique.org. For more options, visit https://groups.google.com/groups/opt_out.
