Thank you for taking the time to respond. I'm probably just not being
very clear.
In Satchmo, there is a view that uses an .rml (ReportLab Markup
Language) to generate a PDF file and return it to the client. This
.rml file is a Django template -- it has Django template markup and is
run through t
On Mon, 2008-05-12 at 10:44 -0400, Joshua 'jag' Ginsberg wrote:
> 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
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
>
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 pat
