Re: idea for using RequestContext by default

On Tue, Jan 5, 2010 at 9:38 AM, Russell Keith-Magee wrote: > To clarify your position Jacob - are you advocating that > shortcuts.render() should return a TemplateReponse? Or are you > suggesting that we add a TemplateResponse *and* a shortcut.render() > that is an analog

Re: idea for using RequestContext by default

On Tue, Jan 5, 2010 at 11:00 PM, Jacob Kaplan-Moss wrote: > On Tue, Jan 5, 2010 at 7:41 AM, Russell Keith-Magee > wrote: >> I haven't taken the temperature of anyone else in the core, but you >> can take it as read that Simon and myself are both +1.

Re: idea for using RequestContext by default

On 5 Jan 2010, at 15:00, Jacob Kaplan-Moss wrote: > On Tue, Jan 5, 2010 at 7:41 AM, Russell Keith-Magee > wrote: >> I haven't taken the temperature of anyone else in the core, but you >> can take it as read that Simon and myself are both +1. The sprint >> this >>

Re: idea for using RequestContext by default

On Tue, Jan 5, 2010 at 7:41 AM, Russell Keith-Magee wrote: > I haven't taken the temperature of anyone else in the core, but you > can take it as read that Simon and myself are both +1. The sprint this > weekend would be a great opportunity to advocate for inclusion of >

Re: idea for using RequestContext by default

Russell Keith-Magee wrote: > Certainly - and Simon made exactly this proposal during the review of > the CSRF work. Simon even provided a sample implementation: > > http://groups.google.com/group/django-developers/msg/b1b3f8854b9ae2b1 Thanks! I keep missing nice things on django-dev@ due to many

Re: idea for using RequestContext by default

On Tue, Jan 5, 2010 at 9:23 PM, Ivan Sagalaev wrote: > Russell Keith-Magee wrote: >> I'm in complete agreement with Simon on this point. I fail to see the >> benefit of decorators in this context. > > I can see one valid point that "render_to" guys have. Which is, >

Re: idea for using RequestContext by default

Russell Keith-Magee wrote: > I'm in complete agreement with Simon on this point. I fail to see the > benefit of decorators in this context. I can see one valid point that "render_to" guys have. Which is, incidentally, has nothing to do with the decorator syntax. An HttpResponse with an opaque

Re: idea for using RequestContext by default

Hi Davor, On Tue, Jan 5, 2010 at 5:06 PM, rebus_ wrote: > Hi, > > This is the "natural" sequence of doing things anyway, i don't see why > would you shuffle it around. > > 1. process stuff into variables > 2. add said variables to a ContextRequest > 3. send said

Re: idea for using RequestContext by default

Hi, This is the "natural" sequence of doing things anyway, i don't see why would you shuffle it around. 1. process stuff into variables 2. add said variables to a ContextRequest 3. send said ContextRequest to a template for rendering. In the example buttman gave in his link [1] you could say

Re: idea for using RequestContext by default

> > I much prefer the @render_to() syntax. This way, I can think of my > > view functions as "context variable creators", instead of "response > > returners". I think of view functions as a sort of context processor > > thats only meant for one specific template. > > I'm in complete agreement with

Re: idea for using RequestContext by default

On Tue, Jan 5, 2010 at 1:57 AM, buttman wrote: > On Jan 2, 5:52 pm, Simon Willison wrote: >> On Dec 30 2009, 10:28 pm, Wim Feijen wrote: >> >> > In the discussions on CSRF there have been several proposals to >> > include

Re: idea for using RequestContext by default

On Jan 2, 5:52 pm, Simon Willison wrote: > On Dec 30 2009, 10:28 pm, Wim Feijen wrote: > > > In the discussions on CSRF there have been several proposals to > > include RequestContext by default in render_to_response or in a > > similar function. As

Re: idea for using RequestContext by default

On Wed, 2009-12-30 at 14:28 -0800, Wim Feijen wrote: > Hello, > > In the discussions on CSRF there have been several proposals to > include RequestContext by default in render_to_response or in a > similar function. As a side note to my previous post, I'd like to > mention my favorite way to do

idea for using RequestContext by default

Hello, In the discussions on CSRF there have been several proposals to include RequestContext by default in render_to_response or in a similar function. As a side note to my previous post, I'd like to mention my favorite way to do this: render_to , see: