Re: intended security model for templates

I also think the "load your tag lib by default for your project" is a good idea. It's a tad magical, but very nice. On Sunday, December 28, 2014 5:26:46 PM UTC-6, Curtis Maloney wrote: > > I certainly like the idea of making public the API to load your tag lib by > default for your project. It'

Re: Formalizing template loader and debug api's

Hi Aymeric, Thanks for the feedback! > Even if it isn’t consistently implemented, the loader API is documented: > > https://docs.djangoproject.com/en/1.7/ref/templates/api/#using-an-alternative-template-language > To sum up: > load_template_source(template_name) —> (template_str

Fellow Report: Dec 28, 2014

Hi all, Here is this week's report. You can see a more readable version of this report at https://code.djangoproject.com/wiki/DjangoFellows/BerkerPeksag#Weekof2014-12-21 Pull requests = Authored = * https://github.com/django/django/pull/3804 -- Converted middleware tests to u

Re: intended security model for templates

Hi Tim, On 12/24/2014 01:35 PM, Tim Graham wrote: > I was hoping to get clarification on what security model we intend to > support for template authors. In ticket #12772 > it's proposed to allow > loading template tags using a dotted Python path. T

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

Hi Alejandro and Russell, On 12/28/2014 07:29 PM, Russell Keith-Magee wrote: > On Sun, Dec 28, 2014 at 8:13 PM, Alejandro Dubrovsky > wrote: >> On Sunday, December 28, 2014 7:23:34 PM UTC+11, Alejandro Dubrovsky wrote: >>> On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote:

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

Hi Alejandro, On Sun, Dec 28, 2014 at 8:13 PM, Alejandro Dubrovsky wrote: > > > > On Sunday, December 28, 2014 7:23:34 PM UTC+11, Alejandro Dubrovsky wrote: >> >> >> On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote: >>> >>> >>> On Sat, Dec 27, 2014 at 9:30 PM, Alejandro D

Re: intended security model for templates

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. Also, I agree that "explicit is better than implicit", and thus reducing

Re: Formalizing template loader and debug api's

Hi Preston, Thanks for working on this ticket — and for bearing with my changes :-) > On 28 déc. 2014, at 06:30, Preston Timmons wrote: > > ## 1. Add new template loader apis > > I tried to solve this patch without changing the template loader apis, but I > eventually decided this was inevitab

Re: Formalizing template loader and debug api's

Hi Unai. Yes, your previous work was helpful for me in developing this solution. Some of Aymeric's recent refactorings have simplified things since you last worked on it as well. Hi Riccardo. Thanks for the suggestion. I don't mind changing the name of get_internal if others agree. That's an ea

Re: Multiple template engines for Django - week 12

Thanks for the explanation. It makes sense to remove select_template. Regards, Michael Manfre On Sun, Dec 28, 2014 at 3:53 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hi Michael, > > > On 28 déc. 2014, at 07:12, Michael Manfre wrote: > > > > If I'm understanding your pos

Re: Formalizing template loader and debug api's

Hello Preston, Il 28/12/2014 06:30, Preston Timmons ha scritto: Hi all, I've been working on #15053, which enables Django template loaders to extend templates of the same name recursively. The most common use-case for this is extending the admin templates without needing to copy the application

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

On Sunday, December 28, 2014 7:23:34 PM UTC+11, Alejandro Dubrovsky wrote: > > > On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote: >> >> >> On Sat, Dec 27, 2014 at 9:30 PM, Alejandro Dubrovsky >> wrote: >>> >>> Hi all, >>> >>> When running a small, low traffic site on s

Re: Formalizing template loader and debug api's

Thanks for your great work Preston, I tried to tackle #15053 myself and I found it was quite a complex issue. I hope I will find some time to look at it in more detail! On Sat, Dec 27, 2014 at 09:30:02PM -0800, Preston Timmons wrote: Hi all, I've been working on #15053, which enables Django t

Re: Multiple template engines for Django - week 12

Hi Michael, > On 28 déc. 2014, at 07:12, Michael Manfre wrote: > > If I'm understanding your post correctly, any potential performance > improvement that a special cased select_template would have would likely be > negated by caching. Sorry, I didn’t explain sufficiently clearly. My reasoning

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote: > > > On Sat, Dec 27, 2014 at 9:30 PM, Alejandro Dubrovsky > wrote: >> >> Hi all, >> >> When running a small, low traffic site on slow cloud servers (eg >> DigitalOcean), it'd be useful to be able to cache pages, not beca