repoze.bfg 1.0a5 was a bit of a browbag release. 1.0a6 has been released to
fix
the feature added in 1.0a5. The changelog is:
1.0a6 (2009-06-29)
==
Bug Fixes
-
- Use ``caller_package`` function instead of ``caller_module``
function within ``templating`` to avoid ne
Anyone ever deploy repoze.bfg on nginx with mod_wsgi? Right now I'm just
using proxy_pass to the paster serve for repoze.bfg, but it just seems more
natural if this could be done using mod_wsgi.
Any thoughts?
Thanks,
Nathan
___
Repoze-dev mailing list
R
To my knowledge, nobody has deployed BFG on ngnix with mod_wsgi.
- C
On 6/29/09 11:59 AM, Nathan Van Gheem wrote:
> Anyone ever deploy repoze.bfg on nginx with mod_wsgi? Right now I'm
> just using proxy_pass to the paster serve for repoze.bfg, but it just
> seems more natural if this could be do
If nobody finds any showstopper bugs, repoze.bfg 1.0 will be released on or
before Monday July 6. Speak now or forever hold your peace wrt to API issues;
after 1.0 the existing APIs will be frozen.
- C
___
Repoze-dev mailing list
Repoze-dev@lists.repo
I'm wondering what the conventional wisdom is for doing bfg apps to
handle crud operations with urls like
/pet -> list pets
/pet/1 -> view pet model, id 1
/pet/1/view
/pet/1/edit -> edit pet model, id 1
Is this something that can be handled well with both traversal and url
dispatch? Are there a
Chris McDonough wrote:
> If nobody finds any showstopper bugs, repoze.bfg 1.0 will be released on or
> before Monday July 6. Speak now or forever hold your peace wrt to API
> issues;
> after 1.0 the existing APIs will be frozen.
No comments on the stability of the release at all, but it seems
Hi Iain
I am using formish with some success at the moment.
You need the latest copy from github, rather than whats in PyPI and if you
want to
use the FileUpload widget you may need to build a custom FileResource
handler (I am running on GAE so write temp files to the filesystem is not an
option )
Hi Iain,
At the time I started using BFG, the options I had didn't quite
attracted me that much so I decided to roll it on my own. My main goal
was to quickly create form widgets from python code using a XML
factory ( template independent ).
Today it's called repoze.etreeform [1] and although it d
On 6/29/09 9:06 PM, Martin Aspeli wrote:
> Chris McDonough wrote:
>> If nobody finds any showstopper bugs, repoze.bfg 1.0 will be released on or
>> before Monday July 6. Speak now or forever hold your peace wrt to API
>> issues;
>> after 1.0 the existing APIs will be frozen.
>
> No comments on th
On 6/29/09 8:26 PM, Iain Duncan wrote:
> I'm wondering what the conventional wisdom is for doing bfg apps to
> handle crud operations with urls like
>
> /pet -> list pets
>
> /pet/1 -> view pet model, id 1
> /pet/1/view
>
> /pet/1/edit -> edit pet model, id 1
>
> Is this something that can be ha
> Let's imagine a view "pets":
>
> from webob import Response
>
> def pets(context, request):
> return Response ('OK')
>
> when a URL comes in that is for a paricular pet:
>
> from webob import Response
>
>
> def pets(context, request):
> if request.subpath:
> petnum = requ
11 matches
Mail list logo
