httpx
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
11warn against
Dec 14, 2025first mention
Sep 11, 2026latest mention
Why people recommend it
“I personally find the httpx API is much cleaner and more composable”
“modern problems (async, http2) required modern solutions (httpx)”
Show 1 more
Caveats and dissent
“isn't really maintained anymore”
“Biggest problem with httpx I see is authors sanity”
Show 2 more
“Better migrate to https://zapros.dev from httpx maintainer”
“Read for yourself: https://github.com/encode/httpx/discussions/3784”
Often compared with
Threads where it came up
- Migrating to HTTPX2 9 mentions
- I Forked Httpx 5 mentions
- Reverting the incremental GC in Python 3.14 and 3.15 2 mentions
- Httpx closing down issues and discussions due to "skewed gender representation" 2 mentions
- Ask HN: What Are You Working On? (December 2025) 2 mentions
- Litelm: LiteLLM Without the Bloat 1 mention
Also written as HTTPX. Data: httpx.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 27
“isn't really maintained anymore”
“The contributors provided the source of the project under these terms, which are stated up front.”
“I personally find the httpx API is much cleaner and more composable”
“Biggest problem with httpx I see is authors sanity”
“Better migrate to https://zapros.dev from httpx maintainer”
“Winner: niquests (4.8x faster by wall clock)”
“Read for yourself: https://github.com/encode/httpx/discussions/3784”
pyreqwest has been delightful so far: https://github.com/MarkusSintonen/pyreqwest It's been a pleasure to use, has a httpx compatibility layer, and it's fast (https://github.com/MarkusSintonen/pyreqwest/blob/main/docs/benchmarks.md)
“Unfortunately that 1.0 work is happening in a private repository.”
“there was no activity on HTTPX”
“The problem with httpx as a dependency is that it's currently working towards a 1.0 release which will be full of breaking changes.”
“I've closed off access to issues and discussions.”
“it's likely caused by a reference cycle”
“Stack: Python, HTTPX, Playwright.”
This sounds like an ideal use case for modshim [0] One of its intended use cases is bridging contribution gaps: while contributing upstream is ideal, maintainers may be slow to merge contributions for various reasons. Forking in response creates a permanent schism and a significant maintenance burden for what might be a small change. Modshim would allow you to create a new Python package containing only the fixes for
thanks, I hope I fixed the https://pythonleiden.nl website now
“modern problems (async, http2) required modern solutions (httpx)”
“niquests easily beat aiohttp just using 10 conn and crush httpx”
“the http landscape is rather scary lately in Python. instead of forking join forces”
“As a mkdocs user and a httpx user”
“Not only is httpx an actual supply chain risk now, but also it shows an unwillingness to fix outstanding bugs and issues”
“Leaves some broken links on their contributing page”
“current stack includes Nuclei, OWASP ZAP, Nmap, httpx”
“Security tools: Nuclei, SQLMap, httpx”
“httpx over requests”
“Httpx/httpcore are abandoned and their connection pooling etc implementations are completely broken”
“Started after getting too annoyed with all the issues httpx has.”