I'm about (or have done by the time you get this - I'm writing this
offline) to commit a bfg branch which reworks the paster templates a
bit. Most of the changes are inspired by the Pylons templates, and all
of them felt like improvements to me. If you approve of the changes I
can take a look a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> Modified: repoze.bfg/branches/wichert-paster/CHANGES.txt
> ==
> --- repoze.bfg/branches/wichert-paster/CHANGES.txt(original)
> +++ repoze.bfg/bra
On 2010-1-6 21:43, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wichert Akkerman wrote:
>
>> Modified: repoze.bfg/branches/wichert-paster/CHANGES.txt
>> ==
>> --- repoze.bfg/branches/wichert-past
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
>> I wouldn't go there, myself: among other things, you lose the ability
>> to do coordination with repoze.retry (e.g., on Postgres' equivalent to a
>> ConflictError).
>
> I'm not sure why you would loose that. I've never use
Details aside, we've decided to do middleware configuration via PasteDeploy,
not in the BFG app factory. I don't see any reason to change that.
Thanks for this work BTW! I'll take a look shortly...
- C
Wichert Akkerman wrote:
> On 2010-1-6 21:43, Tres Seaver wrote:
>> -BEGIN PGP SIGNED ME
OK, I took a look... Besides the paster thing, everything looks ok to me.
Thanks for the work.
Currently there are import errors that would prevent either the alchemy or the
routesalchemy template from actually working. Please run pyflakes on a
rendered version of both templates and commit fi
