On 11/11/10 02:00 , Chris McDonough wrote:
Some of historical Pylons 1 globals don't make sense in the context of
Pyramid, however (such as 'url', because there's no function that
currently behaves exactly like it does). Some historical Pylons globals
are only for backwards compatibility (e.g. "tmpl_context" vs. "c").
Also, some functionality that previously was exposed as a top-level name
now exists as methods/attributes of the request (request.session,
request.route_url, request.registry {registry is a pro-tem substitute
for "g"}).
I feel that g is more similar to BFG's ISettings utility than the
registry. Most of my BFG apps put that utility in the global namespace.
Wichert.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
