Douglas Mayle <doug...@mayle.org> added the comment: The only way I can think to fix this is to create a new generator that wraps the previous one. It calls the wrapped generator once, caches that, and then yields that and any further responses. This allows the original generator to behave the way it did before, and repoze.who can take a look at the status code.
---------- status: unread -> chatting __________________________________ Repoze Bugs <b...@bugs.repoze.org> <http://bugs.repoze.org/issue71> __________________________________ _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
