Re: Proposal: Optional {% default %} clause for the {% for %} template tag

2008-10-30 Thread Mike Panchenko
+1 for {% empty %} I also think this would be very useful On Thu, Oct 30, 2008 at 6:55 AM, dc <[EMAIL PROTECTED]> wrote: > > How about > > {% for item in items %} > {% otherwise %} > {% endfor %} > > form? > > And -1 for the {% else %}. > > > > --~--~-~--~~~---~--~--

Re: Use RequestContext if possible in default 500 error view

2009-04-30 Thread Mike Panchenko
I don't think errors in error templates is a problem specific to Django. I've run into this problem in other frameworks, including when I was messing around with my own in PHP. If you have an exception handler that is itself a candidate for exceptions, you end up with trouble. -1 for showing the u

Re: [GSOC] Multi-DB Update

2009-05-01 Thread Mike Panchenko
I would agree with you on the dict issue, given that some of the backends have custom settings etc. I also agree that this is not really something that matters now - DSNs will need to be parsed into dicts anyway, so you might as well implement the dicts first and then see what the demand is for DS