Use duck-typing to set a quasi-integer response status. #191
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.
This change checks for integer values when setting
response.status
by callingint()
on the supplied value, instead of explicitly checking for a subclass ofint
.This is helpful to me, because I'm writing code that wraps HTTP statuses in a class that defines
__int__()
. I'd like to be able to use WebOb together with this class without having to check whether the Response object accepted the status, or whether I need to callint()
(orstr()
for that matter) and try again.This change additionally removes the need for the "
if ' ' not in value
" check, which assumedvalue
was interpretable byint()
anyway and then performed the same string substitution as the setter forresponse.status_code
.