[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

Tres Seaver added the comment: I have committed an extension of the fix for the 2.0 final release which closes the iterable before raising the RuntimeError when no challenger is available. -- status: chatting -> resolved __ Repoze Bugs

[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

thefunny42 added the comment: Hello, This is indeed fixed for most of the cases, but in case of a missing challenger, close is still not properly called: https://github.com/repoze/repoze.who/blob/master/repoze/who/middleware.py#L1 13 __ Repoze Bugs

[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

thefunny42 added the comment: Thank you for the quick fix :) -- status: resolved -> chatting __ Repoze Bugs __ ___ Repoze-dev mailing list Repo

[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

System message: -- assignedto: -> tseaver nosy: +tseaver __ Repoze Bugs __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists

[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

Tres Seaver added the comment: Fix now checked in, with tests, for both the '__call__' of the middleware and for 'wrap_generator'. -- status: in-progress -> resolved __ Repoze Bugs __ ___

[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

Tres Seaver added the comment: Thanks for the report. -- status: unread -> in-progress __ Repoze Bugs __ ___ Repoze-dev mailing list Repoze-dev

[Repoze-dev] [issue174] repoze.who 2.0a3 doesn't respect the WSGI PEP

New submission from thefunny42 : In middeleware.py, class PluggableAuthenticationMiddleware, method __call__, on line 105, the code consume the application iterator, and doesn't call the method 'close' on it when it is done. Please note that the wrap_generator function need to be fixed as we