Le mardi 17 mai 2016 08:03:52 UTC+2, Carl Meyer a écrit : > > On 05/16/2016 01:48 AM, Claude Paroz wrote: > > > I'm still answering with my naive hat: isn't it possible to simply > > always consider forms in django.forms without requiring anything new in > > INSTALLED_APPS? What would be the problem? (Sorry if I missed a > > discussion about that). > > This is certainly possible, it's just (as Tim says) not clear where > exactly one would implement it without introducing an ugly bidirectional > coupling between forms and templates. It's one thing for form rendering > to now depend on templates, but for template engines (which currently > are configured explicitly and only know about the template directories > you tell them about) to also automatically and unconditionally know > about django.forms (even if you maybe aren't using forms at all -- maybe > you're using the template engine standalone for something else entirely) > doesn't seem right at all. >
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? It may be time for me to dive into the code to stop saying stupid things :-/ Claude -- 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/f30d6a06-7139-4ca0-bb9b-7714d50771a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
