wsgi: improve error message when returning without start_response #444
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today I discovered that if you return from your WSGI function without calling start_response() first, you get a rather unhelpful traceback:
That you have to call start_response() before returning is WSGI 101, but I probably should have been asleep a few hours ago, so it took me a while to work backwards from this traceback to the error in my code. This patch should be a relatively simple change that makes it clear what the issue is.