requests breaking changes
Every breaking API change we have recorded in requests on PyPI: 6 breaking changes in 3 versions. Below are its newest 3 versions, removals and renames first, each with its source.
Newest change March 25, 2026
On this page
2.33.0
- Removed
Python 3.9 is no longer supported, so users on Python 3.9 must upgrade Python to use this release. github.com - Removed
requests.adapters.extract_zipped_paths
requests.adapters.extract_zipped_paths was removed in requests 2.33.0 pypi.org - Behavior changed
requests.utils.extract_zipped_paths
Contents are now extracted to a non-deterministic location to prevent malicious file replacement, so code that relies on a fixed extraction path must change. Default Requests usage is unaffected. github.com
2.32.5
- Removed
Python 3.8 is no longer supported after its end of support. Users on Python 3.8 should stay on requests 2.32.4 or upgrade their Python version. github.com
2.32.4
- Removed
PyPy 3.9 is no longer supported now that it has reached end of support. Move to a supported PyPy version. github.com - Behavior changed
A crafted URL with trusted environment settings could previously pull credentials for another host from a netrc file. Code that relied on that lookup must now match the correct hostname. github.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp