context object

[Mark Ramm]

I think we should provide a proxy for some of the one letter pylons
variables so "c" would become "context." and g would become 'globals'.

Ideally this would live in pylons but if not can do it in turbogears.

--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

[Alberto Valverde]

On Jun 24, 2007, at 5:10 PM, Mark Ramm wrote:

>
> I think we should provide a proxy for some of the one letter pylons
> variables so "c" would become "context." and g would become 'globals'.

+1

>
> Ideally this would live in pylons but if not can do it in turbogears.

+1 for pylons.context and pylons.globals, that would make clearer
that they're really the same objects.

The globals StackedOB is really important since we must get off our
single-app-per-process habits inherited from TG 1.0, having multiple
apps per process (potentially the same app with different
configurations) also requires a slight change in coding style to
avoid global singletons unless they can be shared among apps. The
docs should explain this point clearly to ease migration of 1.0 apps.

Alberto