I know it's an obscure and rather inane question, but if one of the developers would take a moment to comment, I'd be appreciative. Thanks!
-jag On Thu, May 8, 2008 at 3:33 PM, Joshua 'jag' Ginsberg <[EMAIL PROTECTED]> wrote: > Is there a technical reason why django.template.loader.make_origin > returns None unless TEMPLATE_DEBUG is true? Would it not be helpful in > a view to be able to know from whence a template source came from? > > For example, in Satchmo, the view satchmo.shipper.views.displayDoc > they have to know the path of the template in order to pass a relative > path to the template so it can include an icon URI. The view currently > does this by stepping through settings.TEMPLATE_DIRS to find the > template -- which only permits it to be loaded by > django.template.loaders.filesystem and nothing else. I use a > subversion based template loader, and if I could pass the template the > URL relative the origin URL of the template that would be fantastic -- > however without the origin, I can't do that. > > So is there an engineering reason to not return an origin unless we're > debugging templates? Thanks! > > -jag > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
