I took a stab at backwards-compatibility with respect to allowing the admin to work without adding 'django.forms' to INSTALLED_APPS. It seems to work for at least the simple TEMPLATES = 'BACKEND': 'django.template.backends.django.DjangoTemplates', ...} case, although I'm not proud of the code and I'm nervous it's a bit fragile. What do you think of the approach? I thought I'd try something to get the conversation going again. I've been reacting to some tickets based on the assumption that this will get into 1.11 so I'd like to make it happen.
https://github.com/django/django/pull/6498/commits/1eba57277c7168bd491277a14554635bf4efbfc8 On Wednesday, May 18, 2016 at 2:49:52 AM UTC-4, Carl Meyer wrote: > > On 05/17/2016 01:33 AM, Claude Paroz wrote: > > I can imagine that django.forms would then be responsible to tell the > > template engine to add the template source. Maybe this would need a new > > API in the template code? > > Yes, it's certainly possible that we could address this with a new API > in the template engines. That's a more significant change than I had > thought we needed, but it may be the best option. > > I'm happy to work on this issue more, but it's not likely to be until > the PyCon sprints. > > Carl > > > > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/ed0c891a-33f9-4b28-80aa-7a90f2d097e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
