Here's a PR for this change https://github.com/django/django/pull/3897
On Sunday, January 11, 2015 at 4:58:53 AM UTC-5, Aymeric Augustin 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 t
> 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
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
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
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
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:
> >>
>
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
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
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
>
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
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
On Sun, Jan 11, 2015 at 11:33 AM, Collin Anderson
wrote:
> Hi All,
>
> Based on the early feedback, here's a scaled back proposal:
>
> 1. In the project_template settings.py for new projects:
> - Enable the request context processor
> - Keep the auth context processor
> - Remove the rest (you can
>From my experience some reusable apps require (in their documentation) that
specific context_processors are installed. I'm also -0 unless some decent
alternative exists and there's a convincing argument why they aren't a good
feature to have.
Cheers
On Sunday, 11 January 2015 14:33:44 UTC+11,
Hi All,
Based on the early feedback, here's a scaled back proposal:
1. In the project_template settings.py for new projects:
- Enable the request context processor
- Keep the auth context processor
- Remove the rest (you can always install them by hand).
2. Make the admin work without needing spe
On Sun, Jan 11, 2015 at 6:40 AM, 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
> e
I like it from a purity point of view, but I'm dreading updating through it
and replacing every instance of `{{ STATIC_URL }}` in my templates...
I also have a number of small projects which add a custom context processor
which add a certain queryset into the context every time because they form
a
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 context_processors all together and having re
17 matches
Mail list logo
