> > Asking again... I am not sure if the Django Template Language should > evolve new features like this. Is there any prior art in Jinja2? Absent any > other +1's, I guess I would be more comfortable accepting the feature if so. >
I can't say anything about Jinja2, but for existing old projects, that use DjangoTemplates, this feature will be helpful. I mean refactor for large template hierarchy. > The code seems too complicated. Could we reuse os.path handling from the > standard library to simplify it? > I don't think, that os.path is applicable in this case, because template_name != file_name. In fact, this feature must work for any template loader (databases, etc), which have 'hierarchy' concept, and uses '/' as separator for levels of hierarchy. Assuming the feature is accepted, at least a ticket and documentation are > needed to finish the patch. See the patch review checklist: > > https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#patch-review-checklist > Ticket: https://code.djangoproject.com/ticket/26402 -- 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/9886f657-8405-4dd8-9be8-96962ded76a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
