Live data from Hacker News

Migrating to HTTPX2

github.com

61–70 of 119 posts

Re: Migrating to HTTPX2

#61

Earlier quoted context omitted.

https://github.com/encode/httpx/discussions/3784 > I've closed off access to issues and discussions. > I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value. https://www.reddit.com/r/Python/comments/1rl5kuq/anyone_know...

This has happened in many packages contributed to by this person. Mkdocs e.g

unbelievable, how can a single person affect negatively FOSS so much?

I mean really, closing repos? excluding maintainers? committing only on private repos?

This type of behavior should be moderated and banned from any FOSS activity to avoid exactly this situation of becoming a liability.

I've never seen a open source project page without a github link or a git clone ref like this https://www.encode.io/hx/ it is so ridiculous, wasn't that stuff on github? and isn't it anyway there due to over 1k forks?

what's the advantage of having this behaviour? I see it only damaging towards the person, the project and the community.

Re: Migrating to HTTPX2

#62
post #38

Earlier quoted context omitted.

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

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

Maybe they don't feel like sharing their work with the AI bot scrapers until the work is complete.

Re: Migrating to HTTPX2

#66
post #52
post #25

Earlier quoted context omitted.

What happened?

Read for yourself: https://github.com/encode/httpx/discussions/3784 They also effectively killed off MkDocs: https://github.com/mkdocs/mkdocs/discussions/3677

That's easily the strangest self-destruction I've ever seen. "Skewed gender representation"? Not sure how that matters or what the intended effect of salting the earth here was.

Re: Migrating to HTTPX2

#68
post #52
post #25

Earlier quoted context omitted.

What happened?

Read for yourself: https://github.com/encode/httpx/discussions/3784 They also effectively killed off MkDocs: https://github.com/mkdocs/mkdocs/discussions/3677

I feel like that hardly answers anything

Re: Migrating to HTTPX2

#69
post #19

Earlier quoted context omitted.

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

httpx2 is sponsored by Pydantic and has involvement from the new maintainer of Starlette, so it's off to a very strong start.

Kludex is a really good dev
Post reply on HN