"It's six weeks after we forked httpx and named our package httpxyz. Yesterday, the Pydantic people started their own fork, httpx2. TL;DR: while we think httpxyz was definitely needed, we welcome httpx2 and think it should be the 'blessed' fork."
"We did a bunch of work on httpx, merging old open pull requests, forking httpcore, and making serious improvements fixing performance and other issues. The Pydantic fork Straight after we made our fork, I contacted Kludex, who is among other things maintainer of Starlette, about our fork."
"He said that he had also been thinking about doing a fork, but that he might prefer to do one himself, and also that he thought that ours could not get popular because it's on Codeberg instead of on GitHub. I'm not really sure about that last one. While it's true that there are still no big examples of popular Python packages on Codeberg, more and more projects are currently moving there."
"So now that Pydantic, with their skillful team and their powerful ecosystem of packages, is creating their own fork, there is no point really in trying to compete with them. We'll keep httpxyz up; but we will support httpx2 and will urge anyone who is trying to switch away from httpx to consider httpx2."
Six weeks after forking httpx into httpxyz, a new fork called httpx2 has been created by the Pydantic team. The original fork combined merged pull requests, a fork of httpcore, and performance and issue fixes. Concerns were raised about Codeberg hosting, but user adoption was described as driven mainly by PyPI installation rather than forge location. The decision to stop competing was based on the impasse around httpx and the recognition that Pydantic’s ecosystem makes direct rivalry unnecessary. httpxyz will stay available, while support and promotion will shift toward httpx2 for those switching away from httpx.
Read at Tildeweb
Unable to calculate read time
Collection
[
|
...
]