-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
raise_for_status documentation is out of sync #6683
Comments
Hi @dennyb87, thanks for raising this. I responded in a comment here in your PR. If you can provide examples from the official docs hosted on readthedocs, we'd be happy to fix this, but from what I can see currently, this never existed in the Requests documentation. What you provided above is an unmaintained fork we do not have control over. |
Nice catch @nateprewitt . I didn't have time to click through but the screenshot seemed convincing |
Ouch 🤦 that's embarrassing 😅 my bad! apologies for the annoyance 👋 |
No worries, thanks for checking in! |
Not a bug per se, more like a discrepancy between documentation and actual behaviour.
Expected Result
The documentation says
response.raise_for_status()
should return the response for chaining in trivial use cases.Actual Result
The code in the latest version of package doesn't actually allow it, see raise_for_status in models.py
Reproduction Steps
The text was updated successfully, but these errors were encountered: