python-oops-wsgi's proxy start_response callback does not handle a third argument.

[James Henstridge]

According to the WSGI spec, the start_response callback should accept three arguments:

"""
The second parameter passed to the application object is a callable of the form start_response(status, response_headers, exc_info=None). (As with all WSGI callables, the arguments must be supplied positionally, not by keyword.) The start_response callable is used to begin the HTTP response, and it must return a write(body_data) callable (see the Buffering and Streaming section, below).
"""

This means that if a WSGI application tries to report an error to its container (rather than just erroring out completely), that error gets lost and replaced with "TypeError: oops_start_response() takes exactly 2 arguments (3 given)".

Instead, I would expect oops-wsgi to publish an OOPS report based on exc_info and let the application display its error page.

[James Henstridge (jamesh)]

wgrant pointed out to me that r9 fixes this bug.