Re: Formalizing template loader and debug api's

> > The debugging information is two dimensional data: for each level of > template extending, for each template loader, you have one entry — > entries are 4-tuples in your current proposal. Yes, this is correct. Although there may not be an entry for each loader on each level of ext

Re: Support for function application in ORDER BY

Sorry to dig up an old thread, but I've just created a ticket to bring this functionality into django: https://code.djangoproject.com/ticket/24060 Tim Martin, are you interested in bringing this up to date? The alpha freeze for 1.8 is Jan 12th, and I'd really like to get this ready before then.

Re: Formalizing template loader and debug api's

2014-12-29 4:53 GMT+01:00 Preston Timmons : > Did that explain it better? If not, I can try again. :) > Yes, I understand better now. The debugging information is two dimensional data: for each level of template extending, for each template loader, you have one entry — entries are 4-uples in you

Re: status of 1.8 release blockers

On Saturday, December 27, 2014 4:46:52 PM UTC+1, Tim Graham wrote: > > #23745 - Migrations migrate is slow > (new) > Owner: Claude > Status: Patch seems to need improvement so it doesn't cause a regression > with swappable models. > Sorry, but I'm af

Re: intended security model for templates

2014-12-29 0:26 GMT+01:00 Curtis Maloney : > I certainly like the idea of making public the API to load your tag lib by > default for your project. It's there, it's clean, and it's been stable for > a looong time. Of course, the multi-template-engine work may change this. It doesn't. Template