#17199: Base Template Loader should return the origin
---------------------------------+--------------------------------------
     Reporter:  Kronuz           |                    Owner:  nobody
         Type:  Bug              |                   Status:  closed
    Component:  Template system  |                  Version:  SVN
     Severity:  Normal           |               Resolution:  needsinfo
     Keywords:                   |             Triage Stage:  Unreviewed
    Has patch:  1                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+--------------------------------------
Changes (by aaugustin):

 * status:  new => closed
 * version:   => SVN
 * resolution:   => needsinfo


Comment:

 [https://docs.djangoproject.com/en/1.3/ref/templates/api/#using-an-
 alternative-template-language Per the docs]:
 > Custom `Loader` classes should inherit from
 `django.template.loader.BaseLoader` and override the
 `load_template_source()` method, which takes a `template_name` argument,
 loads the template from disk (or elsewhere), and returns a tuple:
 `(template_string, template_origin)`.

 > The `load_template()` method of the `Loader` class retrieves the
 template string by calling `load_template_source()`, instantiates a
 `Template` from the template source, and returns a tuple: `(template,
 template_origin)`

 ----

 I hope this clarifies the expected behavior. With this new information,
 could you explain what Django does wrong exactly, and provide some steps
 to reproduce the issue -- or upload a test case? Thanks!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17199#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to