On Tue, 2012-01-31 at 09:33 -0800, Jonathan Vanasco wrote: > I come from Pylons, where we had the g globals object. I miss it > dearly. > > The Pyramid/Repoze group seems very much into the idea of passing a > request around all the time. I don't like that, mostly from the 'mass > appeal route' , in that its something that just about every other > framework has, and can make Pyramid a bit odd/hard to new people > considering it.
The framework does not require that your application use globals. This makes it possible to run more than one Pyramid application in the same Python process, and makes it more likely that Pyramid can be used "like a library", which makes creating things like a development environment on top of Pyramid more pleasant. *You* can use globals if you like, because any nonglobal can be turned into a global. The inverse is not true, however. I'd put some well-tested well-understood turn-nonglobals-into-globals thing in the cookbook if folks agreed on it (that was the intent of putting the Django-settings-like recipe in there). Pyramid, however, will never require that any framework user depend upon globals. - C -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
