Re: relative path in {% extends "...base.html" %} like relative import

> > > 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 > Documentation:https://github.co

Re: relative path in {% extends "...base.html" %} like relative import

> > Yes, the patch must contain a call to posixpath.join somewhere. This is > tricky to get right, don’t reinvent the wheel! > Agree, posixpath is the best solution. Forgot this module :( -- You received this message because you are subscribed to the Google Groups "Django developers (Contri

Re: relative path in {% extends "...base.html" %} like relative import

> > 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 project

Re: relative path in {% extends "...base.html" %} like relative import

> > Syntax for relative path was changed from ... to ./../ > Anyone can tell me what to do next? Just wait? -- 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 receiv

Re: relative path in {% extends "...base.html" %} like relative import

> > I see you created a pull request: >> https://github.com/django/django/pull/6318 >> > Syntax for relative path was changed from ... to ./../ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscr

Re: relative path in {% extends "...base.html" %} like relative import

> > There are backwards-compatibility concerns as a leading dot can no longer > be used in a template name, though if developers are following the advice > about template namespacing it wouldn't be a problem. > Mimicking for python import paths it's just my proposal. If this violate some guide

Re: relative path in {% extends "...base.html" %} like relative import

> > > Either way, I fail to see how that feature would be really useful. > I was need a refactor for large hierarchy of django templates. Moving branches inside hierarchy is simple, if inheritance uses relative paths. -- You received this message because you are subscribed to the Google Groups

Re: relative path in {% extends "...base.html" %} like relative import

> Hmm... I suppose the closest alternative we have would be to store the > base template name in a variable and pass it in from the view. > If code for support template inheritance lives in views, it's not convenient. Here is code, that implement this feature for Django 1.4/1.9: https://gith

relative path in {% extends "...base.html" %} like relative import

Hi, All. For django.template.backends.django.DjangoTemplates (filesystem and app_directories) it can be very useful. This can be implemented? WBR, Vitaly. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.