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 fixes if you want this to make it
Chris McDonough wrote:
> 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 MESSAGE-----
>>> Hash: SHA1
>>> Wichert Akkerman wrote:
>>>> Modified: repoze.bfg/branches/wichert-paster/CHANGES.txt
>>>> --- repoze.bfg/branches/wichert-paster/CHANGES.txt (original)
>>>> +++ repoze.bfg/branches/wichert-paster/CHANGES.txt Wed Jan 6 12:06:06 2010
>>>> @@ -69,6 +69,18 @@
>>>> - Add a (minimal) tutorial dealing with use of ``repoze.catalog`` in a
>>>> ``repoze.bfg`` application.
>>>> +- Modify PasteScript templates to perform database schema setup and
>>>> + creation of initial content in the setup-app command instead of
>>>> + on every app start.
>>> Seems sensible.
>>>> +- Modify PasteScript templates to support the PasteScript setup-app
>>>> +- Modify PasteScript templates to move the repoze.tm2 endware setup to
>>>> + code.
>>> 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
>> I'm not sure why you would loose that. I've never used repoze.retry, so
>> perhaps I'm missing something. Could you expand a bit on that?
> Repoze-dev mailing list
Repoze-dev mailing list