#257: Keep reference to cherrypy.request in controllers
---------------------------------+------------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  anonymous
     Type:  enhancement          |       Status:  new      
 Priority:  normal               |    Milestone:  1.0      
Component:  TurboGears           |      Version:           
 Severity:  normal               |   Resolution:           
 Keywords:  controller           |  
---------------------------------+------------------------------------------
Changes (by jorge.vargas):

  * milestone:  => 1.0

Old description:

> Controllers (at least those descending from
> turbogears.controllers.Controller) ought to have a local handle on the
> current request, for the sake of easier isolated testing and keeping
> objects near where they are used. This can be done with a 1-line patch to
> line 262 of source:trunk/turbogears/controllers.py (as of [363]). Replace
> what's there ('pass') with:
>
> {{{
> #!python
> request = cherrypy.request
> }}}

New description:

 Controllers (at least those descending from
 turbogears.controllers.Controller) ought to have a local handle on the
 current request, for the sake of easier isolated testing and keeping
 objects near where they are used. This can be done with a 1-line patch to
 
http://trac.turbogears.org/turbogears/browser/trunk/turbogears/controllers.py?rev=363#L262
 (as of [363]). Replace what's there ('pass') with:

 {{{
 #!python
 request = cherrypy.request
 }}}

Comment:

 do we need this?

-- 
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/257>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Tickets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---

Reply via email to