Skip to content

Conversation

@frankie567
Copy link
Contributor

This is a proposal to fix #1067. Nothing really surprising I guess:

  • I applied @florimondmanca suggestion from PR #869 to overload the exception constructor because we must have a Response in this specific case.
  • I also updated the output shown in the QuickStart documentation.

Happy to improve it if needed 🙂

Copy link
Contributor

@lovelydinosaur lovelydinosaur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, yup!

I've been taking a bit of a review of the exceptions and hierarchy today, and have some thoughts on how we might refine that, and also how we might want to deal with when request= or response= should be mandatory/optional, but will treat all that separately to this.

Thanks!

@lovelydinosaur lovelydinosaur merged commit 27b0dbc into encode:master Jul 20, 2020
@lovelydinosaur lovelydinosaur mentioned this pull request Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Raise dedicated exception in .raise_from_status()

2 participants