Tres Seaver tsea...@agendaless.com added the comment:
Released w/ 1.4.
--
status: chatting - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue179
__
___
Chris McDonough chr...@plope.com added the comment:
Hi Graham,
The intent here is to only unwind generators because they may be calling
start_response() as a side effect of the first iteration. While other
iterables might
do that, I think they can lose, because this case is fairly uncommon,
Chris McDonough chr...@plope.com added the comment:
The case this that eagerly unwinding the app_iter is trying to defend against
is (as
you probably know) this one:
def someapp(environ, start_response):
start_response('200 OK', [... headers ...])
for item in
Graham Dumpleton graham.dumple...@gmail.com 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
Chris McDonough chr...@plope.com added the comment:
That's a good idea. I'll just take out the generator check entirely, and put
in a knob.
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue179
__
Chris McDonough chr...@plope.com added the comment:
Grr. Let's try that URL again.
https://github.com/repoze/repoze.profile/commit/8fa63f072de5b14a6b8e4ccf5f78e9
8a62d6cfdc
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue179
New submission from Graham Dumpleton graham.dumple...@gmail.com:
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
