Raise exceptions for unexpected status codes #789

sigmavirus24 · 2018-03-13T01:51:53Z

Also raise exceptions on any 400 or greater status code as discussed in
gh-670

As it stands today, it's hard for people to determine whether None is
returned because that's the API's response or because None is what we
return in the event of a 404 or some other "error"-like status code.

This change undoes that ambiguity and allows people to handle missing or
permission-related problems using exceptions.

Also raise exceptions on any 400 or greater status code as discussed in gh-670 As it stands today, it's hard for people to determine whether None is returned because that's the API's response or because None is what we return in the event of a 404 or some other "error"-like status code. This change undoes that ambiguity and allows people to handle missing or permission-related problems using exceptions.

sigmavirus24 merged commit bbb176b into develop Mar 13, 2018

sigmavirus24 deleted the raise-http-errors branch March 13, 2018 02:11

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Raise exceptions for unexpected status codes #789

Raise exceptions for unexpected status codes #789

Uh oh!

Uh oh!

Uh oh!

Raise exceptions for unexpected status codes #789

Raise exceptions for unexpected status codes #789

Uh oh!

Conversation

Uh oh!

Uh oh!