Re: Perl port of the django template system.

On 26 Dez., 19:10, "Dave Smith" wrote: > There are several use cases that an 'else' simplifies. > Seehttp://code.djangoproject.com/ticket/4534 > andhttp://code.djangoproject.com/changeset/8095for the patch. I included it, might make things easier.. I just saw: {%

Re: Perl port of the django template system.

On Fri, Dec 26, 2008 at 9:54 AM, James Bennett wrote: > > On Fri, Dec 26, 2008 at 11:36 AM, Maluku > wrote: > > Kind of different question: Why is there no {% else %} in {% ifchanged > > %}, I think it might be a help to some people. > >

Re: Perl port of the django template system.

On Fri, Dec 26, 2008 at 11:36 AM, Maluku wrote: > Kind of different question: Why is there no {% else %} in {% ifchanged > %}, I think it might be a help to some people. Because it wouldn't make any sense; the point of 'ifchanged' is to say "I have a special thing

Re: Perl port of the django template system.

On 26 Dez., 08:54, "Adam Findley" wrote: > The real tragedy here is that the Django Template system is great, but > it's name is "tightly coupled" to the Django Project. > > I think DTL is a great and common standard and what people will be looking > for. > > What's wrong

Re: Proposal: deprecate and remove django.utils.simplejson

On Sun, Nov 30, 2008 at 11:50 PM, alex.gay...@gmail.com wrote: > > I think Eric's proposal is dead on, it accomplishes the same task, but > does it without inducing any overhead, since once we assume 2.6 we > inherently assume json is included. So +1 on it as Eric has >