Repository navigation
Use the pydantic maintained fork of httpx, httpx2 #1455
{{title}}
|
Yeah, I saw that and figured I'd wait until it got traction/adoption before swapping. I assume most people won't want both httpx and httpx2 in their dependencies. We could make it a generator option or use optional deps if the ecosystem is split. @johnthagen I'd love your input since you seem to generally know what's going on in the world of Python packages ☺️ |
{{title}}
|
Implemented a draft PR for this at #1461 |
{{title}}
{{editor}}'s edit
{{editor}}'s edit
|
@dbanty My thoughts have changed as of late. I think we should drop httpx entirely and move to httpx2. It's designed as a compatible replacement and httpx has no signs of maintenance. httpx is more of a liability at this point and major other libraries are already moving to httpx2 from httpx. If it makes things simpler (and I'm sure it will) I would recommend that we simply move to httpx2 and mark it as a breaking version change bump. |
{{title}}
|
Here's one example, FastMCP |
{{title}}
|
I agree that it is time to drop the dependency on httpx altogether and move to httpx2. |
{{title}}
|
Yeah, makes sense to me too, it's been popping up everywhere. |
Uh oh!
There was an error while loading. Please reload this page.
{{title}}
Uh oh!
There was an error while loading. Please reload this page.
httpx has not had a release since Dec 24. PydanticAI has taken stewardship of the project by forking it as httpx2 (with recent releases containing bug fixes and support for python 3.14): https://github.com/pydantic/httpx2
It should be a straightforward process to replace httpx in the templates with httpx2. Please let me know if this is acceptable and thanks for making this great tool!