logoalt Hacker News

simonwtoday at 12:24 PM7 repliesview on HN

Anthropic made the same change a few weeks after OpenAI did: https://github.com/anthropics/anthropic-sdk-python/releases/...

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.

The httpx2 project is essentially a fork that promises not to break the existing API, which makes it a more stable dependency to build against.

I wrote a pretty long comment about my concerns for the breaking 1.0 version last year - https://github.com/encode/httpx/discussions/3344#discussionc... - in that comment I recommended the HTTPX project release their 1.0 as a package called httpx2 instead, but a year later we now have an httpx2 (released by a different maintainer) that keeps the old API.


Replies

Aurornistoday at 1:47 PM

> 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.

The httpx maintainer closed off access to issues and discussions on the repo, has been ignoring PRs, and hasn’t updated it in a half a year.

I don’t think there is any reason to consider httpx as a viable project any more. The Pydantic httpx fork has taken its place.

show 1 reply
superzetoday at 1:30 PM

The issue with httpx is that it has an obnoxious and toxic maintainer.

show 1 reply
networkedtoday at 12:49 PM

So I guess HTTPX2 (https://github.com/pydantic/httpx2) is winning out over HTTPXYZ (https://codeberg.org/httpxyz/httpxyz)? I didn't switch to HTTPXYZ after the fork but have been watching it. (What I did was use urllib.request more and bite the Rust bullet with wreq, https://github.com/0x676e67/wreq-python, where it wasn't enough.)

show 2 replies
krzyktoday at 1:45 PM

A bit strange considering "coding is solved".

But seriously, migrating between different libs should be ~free for both Anthropic and OpenAI.

show 1 reply
tonyhart7today at 1:39 PM

"I recommended the HTTPX project release their 1.0 as a package called httpx2 instead, but a year later we now have an httpx2 (released by a different maintainer) that keeps the old API"

wtf is going on

show 1 reply
rolymathtoday at 12:49 PM

The Python community loves confusing versioning.

I mean, obviously Python 2.7 is newer than Python 3.1

I remember swearing I would never migrate to python3 but here we are, I migrated without even feeling it or realizing when (But I do remember django played a big role).

show 6 replies
SimonWAdstoday at 1:26 PM

[flagged]