Closed
Bug 856117
Opened 13 years ago
Closed 13 years ago
Use Django's alternate-template-language support
Categories
(developer.mozilla.org Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jbennett, Unassigned)
Details
(Whiteboard: [specification][type:feature])
What problems would this solve?
===============================
We currently bypass Django's template API entirely since we're using Jinja. But Django now supports plugging in alternate template systems and having them just work off its API (i.e., all of Django's loading/rendering shortcuts will work correctly).
Since that could get rid of a lot of places where we currently have to watch out for whether our version or Django's version is loading/rendering a template, we should look into either writing or using an existing wrapper for doing Jinja in Django this way:
https://docs.djangoproject.com/en/1.4/ref/templates/api/#using-an-alternative-template-language
Who would use this?
===================
N/A.
What would users see?
=====================
N/A.
What would users do? What would happen as a result?
===================================================
N/A.
Is there anything else we should know?
======================================
Updated•13 years ago
|
Priority: -- → P1
Comment 1•13 years ago
|
||
jingo since v0.4 (I think, v0.6 is current) uses this API. Just add jingo.Loader to the top of the TEMPLATE_LOADERS setting and django.shortcuts.render works as expected.
Updated•13 years ago
|
Priority: P1 → P2
| Reporter | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•