On Tue, Oct 30, 2012 at 3:34 PM, Jonathan Vanasco <jonat...@findmeon.com> wrote: > That pattern / functionality is great. I'm just talking about > proactively saying "this name space is reserved for plugins, this > namespace for projects - you can rest assured that as Pyramid grows > and new functionality is added, you will not be affected as long as > you stay within that container". Right now, request.foo is a bit of a > lottery -- from my perspective, chances are you won't add anything to > Pyramid over there, but its not an explicit/futureproof property.
I think it's cool that Pyramid provides a way to do it, but I don't think layering that opinion on top belongs in the core. -- 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.
