Hi all,
I just merged a branch I've been working on for some time to the Pyramid
master branch on Github. The branch was named "twophase", and its goal
was to provide imperative configuration extensibility and two-phase
configuration much like that currently offered by ZCML.
As a result, the ``p
This just caught my eye while reading your mail:
On 12/9/10 09:19 , Chris McDonough wrote:
You might cause it be included within your Pyramid application like so:
from pyramid.config import Configurator
def main(global_config, **settings):
config = Configurator()
On Thu, 2010-12-09 at 10:24 +0100, Wichert Akkerman wrote:
> This just caught my eye while reading your mail:
>
> On 12/9/10 09:19 , Chris McDonough wrote:
> > You might cause it be included within your Pyramid application like so:
> >
> > from pyramid.config import Configurator
> >
> >
On 12/9/10 10:26 , Chris McDonough wrote:
On Thu, 2010-12-09 at 10:24 +0100, Wichert Akkerman wrote:
This just caught my eye while reading your mail:
On 12/9/10 09:19 , Chris McDonough wrote:
You might cause it be included within your Pyramid application like so:
from pyramid.config im
On Thu, 2010-12-09 at 10:27 +0100, Wichert Akkerman wrote:
> On 12/9/10 10:26 , Chris McDonough wrote:
> > On Thu, 2010-12-09 at 10:24 +0100, Wichert Akkerman wrote:
> >> This just caught my eye while reading your mail:
> >>
> >> On 12/9/10 09:19 , Chris McDonough wrote:
> >>> You might cause it be
On Thu, Dec 9, 2010 at 12:19 AM, Chris McDonough wrote:
> As a result, the ``pyramid.configuration`` module has been deprecated
> and exists now only to support backwards compatibility. In its place a
> new ``pyramid.config`` module exists with fundamentally the same API.
> Paster template author
Sure. But such code shouldn't last for very long, because you needn't
support alpha releases of Pyramid forever.
- C
On Fri, 2010-12-10 at 15:41 -0800, Mike Orr wrote:
> On Thu, Dec 9, 2010 at 12:19 AM, Chris McDonough wrote:
> > As a result, the ``pyramid.configuration`` module has been depre
Hello,
it's looking just great!
How do you think, can this behavior be extracted into some pattern for
imperative configuration? I would like to have this in my toolchain in addition
to zope.configuration.
--
Andrey Popp
On Thursday, December 9, 2010 at 11:19 AM, Chris McDonough wrote:
On Sat, 2010-12-11 at 23:49 +0300, Andrey Popp wrote:
> Hello,
>
>
> it's looking just great!
>
>
> How do you think, can this behavior be extracted into some pattern for
> imperative configuration? I would like to have this in my toolchain in
> addition to zope.configuration.
Not sure.. I hav
