Closed cool-RR closed 10 years ago
What do you think?
Still waiting on a response on this one.
Not sure why my reply didn't make it through, but here's the broad strokes: I think this approach is getting away from "explicit is better than implicit" in a way that makes code using shpaml more difficult to maintain.
If you're going to use a *.html
file name and you want it to be processed by the shpaml pre-processor, I can think of a few options which seem clearer and more maintainable:
#!shpaml
on the other hand you can always do it like this:
auth/index.html
(original source)
{% extends "auth/index.shpaml" %}
then you create auth/index.shpaml
which extends the template that the original auth/index.html
extended:
% extends "admin/base_site.html"
…template code here...
Ah, the extends solution looks ideal to me. Thanks!
This'll be super userful when dealing with packages like django.contrib.auth that already defined their template names which can't be changed to .shpaml