5 ms·

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

by simonw 2mo ago

Anthropic made the same change a few weeks after OpenAI did: https://github.com/anthropics/anthropic-sdk-python/releases/tag/v1.0.0 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#discussioncomment-14170874 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.

rolymath 2mo ago
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).
- Longwelwind 2mo ago
  Isn't that whole point of semantic release? Minors and hotfixes allow you to release a new version for an older release (like if you released 3.7 but you found a bug present in 3.4, you can release 3.4.1 which would be newer than 3.7), making it possible to have multiple supported versions at the same time.
- chme 2mo ago
  That isn't confusing at all, if you know how maintained stable releases work. Happens with the Linux kernel as well.
- yard2010 2mo ago
  Tangibly related, did you know that odd versions of node don't get LTS, I found it odd at first
- hk__2 2mo ago
  There are a lot of large projects where X.1 is newer than Y.0. You release a new major version for breaking changes, but you backport security changes to previous major releases as well.
- paulddraper 2mo ago
  That’s probably the worst example you could have chosen. You shouldn’t assume anything about relative date of 2.7 and 3.1.
- jubilanti 2mo ago
  Just read https://semver.org/ https://semver.org/
networked 2mo ago
So I guess HTTPX2 (https://github.com/pydantic/httpx2 https://github.com/pydantic/httpx2) is winning out over HTTPXYZ (https://codeberg.org/httpxyz/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 https://github.com/0x676e67/wreq-python, where it wasn't enough.)
- simonw 2mo ago
  httpx2 is sponsored by Pydantic and has involvement from the new maintainer of Starlette, so it's off to a very strong start.
  - fnord123 2mo ago
    Kludex is a really good dev
    - glitch253 2mo ago
      He's a freaking GOD
- kelvinjps10 2mo ago
  in their README >Important We started this fork because there was no activity on HTTPX, a very popular Python HTTP library. A few weeks later, Pydantic started their own fork called HTTPX2. We decided to embrace this and support HTTPX2. We're upstreaming our fixes to HTTPX2 and in our opinion it should be the "blessed" fork. Pydantic can make this more successful than we ever can. See also https://tildeweb.nl/~michiel/httpx2.html https://tildeweb.nl/~michiel/httpx2.html Thanks for all your support! Sander & Michiel
  - NewJazz 2mo ago
    It is too bad because httpxyz is absolutely the better name.
SimonWAds 2mo ago
[flagged]
superze 2mo ago
The issue with httpx is that it has an obnoxious and toxic maintainer.
- portly 2mo ago
  What happened?
  - beanjuiceII 2mo ago
    was probably chewing bubble gum on the wrong sidewalk
    - jatora 2mo ago
      this made me laugh even though i dont think i even get it. can you explain this please lol
      - beanjuiceII 2mo ago
        people think other people are 'toxic' for the silliest of things most times; and this person is saying some maintainer is toxic to put it out there but provides no information as to why.. so i figured my context is as good as theirs
        nozzlegear 2mo ago
        > people think other people are 'toxic' for the silliest of things most times Do they?
  - t098i3 2mo ago
    Read for yourself: https://github.com/encode/httpx/discussions/3784 https://github.com/encode/httpx/discussions/3784 They also effectively killed off MkDocs: https://github.com/mkdocs/mkdocs/discussions/3677 https://github.com/mkdocs/mkdocs/discussions/3677
    - 2mo ago
tonyhart7 2mo ago
"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
- ClikeX 2mo ago
  Open Source disputes.
krzyk 2mo ago
A bit strange considering "coding is solved". But seriously, migrating between different libs should be ~free for both Anthropic and OpenAI.
- simonw 2mo ago
  A migration document like this one is how you get that ~free upgrade - it's something you can point an agent at.
Aurornis 2mo ago
> 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.
- simonw 2mo ago
  HTTPX stable hasn't had a release since December 2024, but there have been two dev releases of the 1.0 branch this month (after a gap since September 2025.) Unfortunately that 1.0 work is happening in a private repository. https://pypi.org/project/httpx/#history https://pypi.org/project/httpx/#history
  - Aurornis 2mo ago
    > Unfortunately that 1.0 work is happening in a private repository. That’s even more reason to consider it non-viable. There is no reason to encourage or support this type of behavior in a project. It is their right to do with it as they please, but I’m not interested in a project that functions like this. The forks are continuing to operate like true community projects.
    - jgalt212 2mo ago
      Maybe they don't feel like sharing their work with the AI bot scrapers until the work is complete.
      - tredre3 2mo ago
        That is a legitimate feeling, but to spite the trillion dollars company he also hurts thousands of regular developers. He doesn't owe those developers anything, of course, but likewise they do not owe him loyalty and thus since an open fork exists, his project will die. Killing the project is also his right, but people also have a right to be upset by his passive aggressive behavior. Just announce that you're shutting down the project and move on, don't waste our time.
jelenzelen 2mo ago
Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 https://github.com/encode/httpx/discussions/3784. I do not even understand what is his problem (too much or too little woke internet?).

by simonw 2mo ago

rolymath 2mo ago

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

Longwelwind 2mo ago
Isn't that whole point of semantic release? Minors and hotfixes allow you to release a new version for an older release (like if you released 3.7 but you found a bug present in 3.4, you can release 3.4.1 which would be newer than 3.7), making it possible to have multiple supported versions at the same time.
chme 2mo ago
That isn't confusing at all, if you know how maintained stable releases work. Happens with the Linux kernel as well.
yard2010 2mo ago
Tangibly related, did you know that odd versions of node don't get LTS, I found it odd at first
hk__2 2mo ago
There are a lot of large projects where X.1 is newer than Y.0. You release a new major version for breaking changes, but you backport security changes to previous major releases as well.
paulddraper 2mo ago
That’s probably the worst example you could have chosen. You shouldn’t assume anything about relative date of 2.7 and 3.1.
jubilanti 2mo ago
Just read https://semver.org/ https://semver.org/

networked 2mo ago

So I guess HTTPX2 (https://github.com/pydantic/httpx2 https://github.com/pydantic/httpx2) is winning out over HTTPXYZ (https://codeberg.org/httpxyz/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 https://github.com/0x676e67/wreq-python, where it wasn't enough.)

simonw 2mo ago
httpx2 is sponsored by Pydantic and has involvement from the new maintainer of Starlette, so it's off to a very strong start.
- fnord123 2mo ago
  Kludex is a really good dev
  - glitch253 2mo ago
    He's a freaking GOD
kelvinjps10 2mo ago
in their README >Important We started this fork because there was no activity on HTTPX, a very popular Python HTTP library. A few weeks later, Pydantic started their own fork called HTTPX2. We decided to embrace this and support HTTPX2. We're upstreaming our fixes to HTTPX2 and in our opinion it should be the "blessed" fork. Pydantic can make this more successful than we ever can. See also https://tildeweb.nl/~michiel/httpx2.html https://tildeweb.nl/~michiel/httpx2.html Thanks for all your support! Sander & Michiel
- NewJazz 2mo ago
  It is too bad because httpxyz is absolutely the better name.

SimonWAds 2mo ago

[flagged]

superze 2mo ago

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

portly 2mo ago
What happened?
- beanjuiceII 2mo ago
  was probably chewing bubble gum on the wrong sidewalk
  - jatora 2mo ago
    this made me laugh even though i dont think i even get it. can you explain this please lol
    - beanjuiceII 2mo ago
      people think other people are 'toxic' for the silliest of things most times; and this person is saying some maintainer is toxic to put it out there but provides no information as to why.. so i figured my context is as good as theirs
      - nozzlegear 2mo ago
        > people think other people are 'toxic' for the silliest of things most times Do they?
- t098i3 2mo ago
  Read for yourself: https://github.com/encode/httpx/discussions/3784 https://github.com/encode/httpx/discussions/3784 They also effectively killed off MkDocs: https://github.com/mkdocs/mkdocs/discussions/3677 https://github.com/mkdocs/mkdocs/discussions/3677
  - 2mo ago

tonyhart7 2mo ago

"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

ClikeX 2mo ago
Open Source disputes.

krzyk 2mo ago

A bit strange considering "coding is solved". But seriously, migrating between different libs should be ~free for both Anthropic and OpenAI.

simonw 2mo ago
A migration document like this one is how you get that ~free upgrade - it's something you can point an agent at.

Aurornis 2mo ago

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

simonw 2mo ago
HTTPX stable hasn't had a release since December 2024, but there have been two dev releases of the 1.0 branch this month (after a gap since September 2025.) Unfortunately that 1.0 work is happening in a private repository. https://pypi.org/project/httpx/#history https://pypi.org/project/httpx/#history
- Aurornis 2mo ago
  > Unfortunately that 1.0 work is happening in a private repository. That’s even more reason to consider it non-viable. There is no reason to encourage or support this type of behavior in a project. It is their right to do with it as they please, but I’m not interested in a project that functions like this. The forks are continuing to operate like true community projects.
  - jgalt212 2mo ago
    Maybe they don't feel like sharing their work with the AI bot scrapers until the work is complete.
    - tredre3 2mo ago
      That is a legitimate feeling, but to spite the trillion dollars company he also hurts thousands of regular developers. He doesn't owe those developers anything, of course, but likewise they do not owe him loyalty and thus since an open fork exists, his project will die. Killing the project is also his right, but people also have a right to be upset by his passive aggressive behavior. Just announce that you're shutting down the project and move on, don't waste our time.

jelenzelen 2mo ago

Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 https://github.com/encode/httpx/discussions/3784. I do not even understand what is his problem (too much or too little woke internet?).