Neaten up our try...except structure for ensuring responses #1525
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.
More consistent structuring for ensuring we don't leave unclosed responses hanging in exception cases.
Essentially, any time we're internally calling a method that returns a response, we want to follow that with a
try...except...
block, and ensure we close the response if an exception occurs.This pull request neatens up that behaviour, and likely closes some unseen edge cases as a result.