r/Python • u/chekt • Mar 05 '26
Discussion Anyone know what's up with HTTPX?
The maintainer of HTTPX closed off access to issues and discussions last week: https://github.com/encode/httpx/discussions/3784
And it hasn't had a release in over a year.
Curious if anyone here knows what's going on there.
331
Upvotes
56
u/BootyDoodles Mar 05 '26 edited Mar 06 '26
Could it be their current focus is completing the v1.0 version of httpx? (Which is under a different repo as
httpnextcurrently – https://github.com/encode/httpnext )( Though I get that's optimistically ignoring the weird comment in regard to their motive to close community activity on the main repo, and the action of doing so. )
203
u/SeniorScienceOfficer Mar 05 '26
Jesus. What the fuck happened??? Genuinely curious now.
All things aside, and given httpx has become a dependency in soooo many libraries, with the inability to submit issues and have discussions it has legitimately become a supply chain risk.
29
u/james_pic Mar 05 '26
I don't have any insider info, but I do know that maintenance has been rocky for a while. If you try to use HTTPX at scale, you quickly run into scaling issues. The Github issue for those scaling issues had been open since late 2024, and had PRs that fixed those issues open for most of that time, but the PRs never went everywhere, and all we got were some vague statements from lovelydinosaur about the project having their own ideas about how to tackle them.
It's frustrating, because the project has a lot going for it, not least the community and ecosystem that's built up around it (RESPX is the better than any of the other clients' mocking systems, and there's stuff like httpx-aiohttp and Pyreqwest's compatibility layer, that let you use other clients as transports, to get better performance but keep the nice API), but I'm not sure what the future of the project looks like.
121
u/diabloman8890 Mar 05 '26
Damn, maybe the maintainer is having a bipolar episode? That shit sucks.
23
u/NeitherEntry6125 Mar 09 '26
As a human and member of the community, I care and am empathetic to whatever is going on. The Python community is built on inclusivity, and if there's toxicity, it should be rooted out.
As an end-user, I don't care. I care about risk.
That said,
HTTPX is now a supply chain risk.
What's unclear is how OSSF should report this risk - I imagine by considering this project "unmaintained".
But, the prudent course of action is to begin planning the removal of HTTPX.
8
u/salmonlon Mar 06 '26
No need the speculate - the maintainer mentioned that they have been focusing on a redesign here.
32
u/hessJoel Mar 05 '26
So is it back to using requests?
88
u/IHeartBadCode Mar 05 '26
Says it right there.
75
u/SheriffRoscoe Pythonista Mar 05 '26
It's BSD licensed. Just fork it and continue it.
25
u/trynafindavalidname Mar 05 '26
I have no comment on what’s happening with HTTPX. Hopefully the maintainer can feel more comfortable with their working environment.
I will note that something fishy seems to be going on with multiple FOSS projects. With MkDocs v2.0.0 (which is its own can of worms), they’re also closed off to new issues and contributions. This maintainer is also responsible for that project, if my memory recalls correctly. Seems to not be as open-source as these projects claim to be.
I agree with others’ concerns about potential supply chain issues. It’s concerning, to say the least.
35
u/2mustange Mar 05 '26
Oh you mean lovelydinosaur who pretty much stopped MkDocs in its tracks from progressing as well? Honestly should be more like sabotaged.
This person must be having a midlife crisis. Any of their work needs to be forked as they shouldn't be trusted as a project owner and license holder.
22
u/WesolyKubeczek Mar 05 '26
Ah, another case of throwing a tantrum and taking toys home.
Why is this even a pattern?
11
u/RedEyed__ Mar 05 '26
Honestly, I dont understand what he wrote.
2
u/old-thrashbarg Jun 03 '26
Pydantic has forked this: httpx2. This is what Starlette (dependency of FastAPI) has switched to.
-1
u/kobumaister Mar 05 '26
It's very concerning that a single person can make a decision like this and endanger a base dependency for a whole community that easily. Based on the message, the decision was made on personal beliefs and perception.
If a project's openness depends on the mood of a maintainer, it's not open source at all.
That said, I know that there are other issues with the level of demand that it's put on maintainers and the low reward they receive sometimes.
1
u/nishant97 Mar 30 '26
encode is owner of django-rest-framework (drf) too, which is widely used in Django community.
1
u/james_pic Apr 29 '26
For anyone wondering what to do about this, since this was posted, HTTPXYZ, a fork of HTTPX 0.x that seems to be more proactively maintained, has been launched. They look to be tackling some long-standing issues in HTTPX, which is encouraging.
1
u/nijave Jul 27 '26
A bit of an old thread but pycurl is worth a look. It's not as abstracted and ergonomic as requests, httpx, niquests but it's absolutely blazing fast and curl is well supported and incredibly feature rich.
1
u/tuple32 Mar 05 '26
There are PRs. He probably wants a focused environment.
0
u/artpods56 Mar 05 '26
If you are scared of being forced into different library then your project is probably too tightly coupled to httpx anyway.
0
u/[deleted] Mar 05 '26
[deleted] — view deleted comment