#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 mramm):
Replying to [comment:4 chrisz]:
> `url` is already inside tg, but it is outside as well; the same is true
for `request`; `response` is only outside tg, `config` only inside. I have
the feeling that this is all pretty arbitrary and really needs some clean
up.
>
> At the top level I think we should only have `tg` and the one-letter-
variables from Pylons.
The reason for this is that pylons places the url, request, and response
outside, so all "root" level variables in the template are there to match
what Pylons does by default. And all the ones inside are copies of what
was in tg1.
I am more than willing to put everything inside of tg, and document it as
different from both tg1 and tg2, but there is reasoning behind why it is
the way it is now.
--
Ticket URL: <http://trac.turbogears.org/ticket/2194#comment:9>
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
-~----------~----~----~----~------~----~------~--~---
