#2194: Turbogears overrides controller return values for templates
------------------------+---------------------------------------------------
Reporter: kikidonk | Owner: faide
Type: defect | Status: new
Priority: highest | Milestone: 2.0b6
Component: TurboGears | Version: trunk
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by jorge.vargas):
I think we will need the namespacing, It's the most obvious way to get
around this. Now keep in mind both pylons and TG are doing this. I found a
related issue working with another ticket, as you can tell my quick-dirty
patch is dirty mainly because of this namespacing issue
http://trac.turbogears.org/ticket/2212
Which is why I'm not totally sold on the namespace because we'll have to
store, all of the following variables in there.
['tg','h','helpers','c','url','request','response','tmpl_context']
I think we should consider other options
1- reserved keywords, we'll prevent users from using vars TG itself is
using (generating an error)
2- overwrite TG defaults by user vars (warning if a user sends a response
variable to the template things will get screwed, or h, that will break
even in more colourful wants than url.
--
Ticket URL: <http://trac.turbogears.org/ticket/2194#comment:8>
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.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
