Repository navigation
Make error responses raise an HTTPError by default - #754
Closed
florimondmanca wants to merge 1 commit into
Closed
florimondmanca wants to merge 1 commit into
florimondmanca wants to merge 1 commit into
Conversation
florimondmanca
added
user-experience
Contributor
Author
|
Closing for now per #752 (comment). |
Kludex
referenced
this pull request
in pydantic/httpx2
May 11, 2026
* Move configurations to pyproject.toml, use ruff instead of flake8, autoflake and isort * Add --fix for ruff * Add ruff to requirements * Add black * Fix omit and include * Add isort * Add show-source option to ruff check * Drop isort configs Co-authored-by: Zanie <contact@zanie.dev> * Remove autoflake from scripts/lint --------- Co-authored-by: Zanie <contact@zanie.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #752, includes both docs and implementation.
We could also introduce the
raise_for_statusparameter first, and then switch it to on-by-default, though I think if that's what we'd do then it makes sense to have everything in one PR.