Yes, that's always the fall back, isn't it?

I'll look at Jinja, as I didn't realize there was such a fork.
Apparently I'm not the only one who thinks this way.

I'm concerned with how well a solution like this tracks the Django
release.

However, simply dodging the question doesn't address the original point:
why does Django adhere to such a nannyish philosophy, and how do you
solve the problem I presented *within Django* in a reasonable way?

Thanks and regards,
-scott anderson


On Thu, 2007-09-13 at 23:46 -0500, James Bennett wrote:
> On 9/13/07, Scott Anderson <[EMAIL PROTECTED]> wrote:
> > What I'm hoping, however, is that this missive was moot, because you'll
> > say, "no, Scott, you should just do *this*:", followed by an elegant and
> > reasonable solution that I, as a relative newcomer to Django, have not
> > yet considered. Here's to your reply, and cheers!
> 
> OK, here you go:
> 
> Use another template system, either site-wide or for the cases where
> the Django template system isn't doing what you need. It's not hard to
> do this, and it opens up the possibility of using any or all of the
> vast number of Python template systems available.
> 
> The Django template system, at this point, will almost certainly
> *never* include the type of functionality you're asking for, so use
> another template system that does or that's more willing to bend its
> philosophy to suit what you want. If you like the rest of the Django
> template system I'd suggest you try Jinja, which started as a fork of
> Django's template system and so is nearly feature-for-feature
> identical, but adds arbitrary Python expressions.
> 
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to