Re: simplifying the default template context_processors

2015-01-11 Thread Aymeric Augustin
> Le 12 janv. 2015 à 05:25, Russell Keith-Magee a > écrit : > > For more irony - the removal of TEMPLATE_CONTEXT_PROCESSORS was the one that > bugged me most from the original template cleanup :-) In hindsight it was a mistake. -- Aymeric. -- You received this message because you are subsc

Re: simplifying the default template context_processors

2015-01-11 Thread cyclebelfast
On 12/01/15 05:16, Russell Keith-Magee wrote: On Mon, Jan 12, 2015 at 12:59 PM, mailto:cyclebelf...@gmail.com>> wrote: On 10/01/15 22:40, Collin Anderson wrote: Hi All, In talking to Aymeric and other developers, we're starting to think about the usefulness of glob

Re: simplifying the default template context_processors

2015-01-11 Thread Russell Keith-Magee
On Mon, Jan 12, 2015 at 12:59 PM, wrote: > On 10/01/15 22:40, Collin Anderson wrote: > >> Hi All, >> >> In talking to Aymeric and other developers, we're starting to think >> about the usefulness of global template context_processors. It seems to >> us that ideally you should only need the "reque

Re: simplifying the default template context_processors

2015-01-11 Thread cyclebelfast
On 10/01/15 22:40, Collin Anderson wrote: Hi All, In talking to Aymeric and other developers, we're starting to think about the usefulness of global template context_processors. It seems to us that ideally you should only need the "request" context processor. You could even imagine removing cont

Re: simplifying the default template context_processors

2015-01-11 Thread Russell Keith-Magee
On Mon, Jan 12, 2015 at 10:28 AM, Carl Meyer wrote: > Hi Russ, > > On 01/11/2015 05:20 PM, Russell Keith-Magee wrote: > >> Without having spent much time to research the consequences — it's on my > >> TODO list but Collin brought it up before I investigated — my straw man > >> proposal is: > >> >

Fellow Report: Jan 11, 2015

2015-01-11 Thread Berker Peksağ
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#Weekof2015-01-05 Pull requests = In progress = * https://github.com/django/django/pull/3467 -- Fixed #21429 -- Added builti

Re: simplifying the default template context_processors

2015-01-11 Thread Carl Meyer
Hi Russ, On 01/11/2015 05:20 PM, Russell Keith-Magee wrote: >> Without having spent much time to research the consequences — it's on my >> TODO list but Collin brought it up before I investigated — my straw man >> proposal is: >> >> TEMPLATES = [ >> { >> 'BACKEND': 'django.template.bac

Re: simplifying the default template context_processors

2015-01-11 Thread Russell Keith-Magee
On Sun, Jan 11, 2015 at 5:58 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 11 janv. 2015, at 09:43, Russell Keith-Magee > wrote: > > > However, I'd still have some concerns about a project template that took > out all the "useful" utilities, and required users to remember

Re: simplifying the default template context_processors

2015-01-11 Thread Aymeric Augustin
On 11 janv. 2015, at 09:43, Russell Keith-Magee wrote: > However, I'd still have some concerns about a project template that took out > all the "useful" utilities, and required users to remember the exact spelling > of half a dozen builtins to have functionality that would have historically >

Re: simplifying the default template context_processors

2015-01-11 Thread Russell Keith-Magee
On Sunday, January 11, 2015, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 11 janv. 2015, at 06:20, Russell Keith-Magee > wrote: > > > TEMPLATE_CONTEXT_PROCESSORS isn't in the project template at present; it > is a default value inherited from global settings > > (…) > > ISTM

Re: simplifying the default template context_processors

2015-01-11 Thread Aymeric Augustin
On 11 janv. 2015, at 06:20, Russell Keith-Magee wrote: > TEMPLATE_CONTEXT_PROCESSORS isn't in the project template at present; it is a > default value inherited from global settings > (…) > ISTM that we can't pare that down with just auth and request without having > some pretty profound conseq