Merge lp:~james-w/python-oops-wsgi/start_response-exc_info into lp:python-oops-wsgi
Proposed by
James Westby
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 35 | ||||
Proposed branch: | lp:~james-w/python-oops-wsgi/start_response-exc_info | ||||
Merge into: | lp:python-oops-wsgi | ||||
Diff against target: |
47 lines (+18/-1) 2 files modified
oops_wsgi/middleware.py (+1/-1) oops_wsgi/tests/test_middleware.py (+17/-0) |
||||
To merge this branch: | bzr merge lp:~james-w/python-oops-wsgi/start_response-exc_info | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Collins (community) | Needs Fixing | ||
Review via email: mp+90031@code.launchpad.net |
Description of the change
Hi,
As discussed exc_info shouldn't be passed as a keyword argument.
Thanks,
James
To post a comment you must log in.
35 + step = iterator.next()
36 + # the client pipe is closed or something - we discard the iterator
37 + del iterator
38 + gc.collect()
39 + return step
I think this is more complex than needed - a simple list() should do the trick; you probably want an assert on the content of the collected calls as well(e.g. nothing demonstrates that exc_info *was* supplied).
matchers. MatchesExceptio n(ValueError( 'Boom, yo')) will probably be an aid there.
Oh, and there is a typo in the test function name