> In my view, the problems with WSGI are that it has an unpythonic API (see: start_response and environ),
Why do you find `start_response` unpythonic?
Why do you find `start_response` unpythonic?
> We could remove start_response and the writer that it implies.
I searched for `wsgi start_response issues` and didn't get anything useful. Care to point out what's the fuss with start_response and why it's unpythonic?
"Note that in the WSGI 2 calling protocol, you would simply modify your return values, rather than needing to create a function and pass it down the call chain."
http://mail.python.org/pipermail/web-sig/2009-November/00424...