On 10/30/2012 04:49 PM, Michael Merickel wrote:
On Tue, Oct 30, 2012 at 3:34 PM, Jonathan Vanasco 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
On Tue, Oct 30, 2012 at 3:34 PM, Jonathan Vanasco 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
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".
On Tue, Oct 30, 2012 at 1:17 PM, Jonathan Vanasco wrote:
> 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 develo
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
