Douglas Mayle <> 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 <>
Repoze-dev mailing list

Reply via email to