The past few updates to Pyramid have had a few changes around the Request object - new attributes, new functionality to add attributes, etc.
With that, combined with the best-practice of passing the Request object around during the request lifecycle, I wanted to suggest creating a 'project' and 'plugin' namespace under request , so that (moving forward) as people develop plugins or write app specific request attributes there is no issue for collision against each other or future Pyramid releases. The general idea would be this: request.project = reserved for your app ( or request.projects.project_name ). do what you want. request.plugins = reserved for plugins that need to attach data to the request object. ex: request.plugins.sqlalchemy The main idea is that instead of using 'set_property', you'd use 'set_project_property' or similar. Not suggesting that we drop the current scenario, just that - the request object has a lot of stuff in it now - i can see the request object's attributes/methods growing as Pyramid matures - i fear namespace collision. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@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.
