Tim Hoffman wrote:
> Hi Chris
>
> I think this is a good direction to go in. I am already starting to
> do something similair this with repoze (I am still on 1.0.1) but plan
> to upgrade in the next few weeks,.
>
> The advantage of this style of configuration really comes into its own
> when yo
I agree this is an awesome direction to go in. I've always thought of
configuration myself as a refactoring done when the app gets complex
enough. Starting off with the assumption that your app will get
complex enough to warrant xml files/ runtime dependencies is a hard
sell when you are starting
Hi Chris
I think this is a good direction to go in. I am already starting to
do something similair this with repoze (I am still on 1.0.1) but plan
to upgrade in the next few weeks,.
The advantage of this style of configuration really comes into its own
when you are running on appengine.
With ap
Hi folks,
I've been working on the next minor revision to repoze.bfg, which will be 1.2.
1.2 will be a slightly more important release than the previous 1.1 release,
because it involves exposing an "imperative" API for configuration (adding
routes/views, etc).
In particular, it means that the
