Graham Dumpleton added the comment:
Or have it check a WSGI environ flag to modify behaviour as to whether consume
flatten iterable/generator. I would rather not have to modify code every time
if you
are going to make it so doesn't track iterable/generator and close() call. I
can
Graham Dumpleton added the comment:
I would say that using:
def __iter__(self):
for item in self.generator:
yield item
would be a fairly common recipe for implementing WSGI middleware wrappers
wouldn't it. The generator which is wrapped by this could just as we
New submission from Graham Dumpleton :
In:
http://bugs.repoze.org/issue169
Tres said:
"""
Thanks for the report! I agree that your suggested solution is probably
the correct one, with the exception that I would have it apply 'list()'
only for results which were g
On May 26, 12:02 pm, Yuan HOng wrote:
> Hi,
>
> I have an application with the following routing configuration:
>
> path="wishlist"
> name="wishlistjson"
> header="Content-Type:application/json;*"
> xhr="true"
> factory=".order.wishlistview.wishlist_f
On Apr 8, 8:04 am, Chris McDonough wrote:
> repoze.bfg 1.2.1 has been released.
>
> Get it via:
>
> easy_install -ihttp://dist.repoze.org/bfg/1.2/simplerepoze.bfg
>
> Or similarly via PyPI.
>
> This is a bugfix-only release. The docs athttp://docs.repoze.org/bfg/1.2/
> have been updated.
>
>
On Nov 3, 8:33 am, Malthe Borch wrote:
> 2009/11/2 Martin Aspeli :
>
> > I think it's better to use top-level namespaces to indicate ownership,
> > if nothing else to avoid the chance of things clashing. For the repoze
> > project to "claim" the wsgi.* namespace seems both a bit presumteuous
> >
On Nov 2, 9:17 am, Chris McDonough wrote:
> repoze.bfg 1.1b1 has been released.
>
> ...
>
> - If a BFG app that had a route matching the root URL was mounted
> under a path in modwsgi, ala ``WSGIScriptAlias /myapp
> /Users/chrism/projects/modwsgi/env/bfg.wsgi``, the home route (a
> rout
