Live data from Hacker News

Httpx closing down issues and discussions due to "skewed gender representation"

github.com

11–15 of 15 posts

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#11
post #6

Earlier quoted context omitted.

How is _your_ supply chain a concern of this open source developer?

_My_ supply chain is not a big deal, lol. But this is HTTPX. A network library that has a considerable number of users. When I say _considerable_, I'm essentially saying _nearly every_ big tech. The one I can tell for sure is OpenAI (not a fan of them though). Remember xz attack?

Why can nearly every big tech take care of their supply chain? :)

Clearly, the maintainer doesn't want to do this job anymore, and it's not a requirement when releasing your code to also do stuff unrelated to programming.

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#12
This is yet another of several reasons why we've switched from httpx to pyreqwest[0]. Not only is httpx an actual supply chain risk now, but also it shows an unwillingness to fix outstanding bugs and issues, which is problematic in a project that has been adopted by so many users.

For those migrating, pyreqwest provides a completely httpx-compatible wrapper.[1]

  [0]: https://github.com/MarkusSintonen/pyreqwest
  [1]: https://github.com/MarkusSintonen/pyreqwest/tree/main/python/pyreqwest/compatibility/httpx

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#13
post #5

Earlier quoted context omitted.

Then why not provide one yourself?

Forking is a good option for companies, but not a good option for sole developers: one doesn't have that much energy. Switching to other libraries like requests and aiohttp and supporting them by contributing is clearly a better option.

https://github.com/MarkusSintonen/pyreqwest is a great alternative, much more performant than requests/httpx/aiohttp, and provides an easy httpx compatible wrapper for migration.

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#14
post #5

I personally treat it as a supply chain risk, as there are no longer any way to report any bugs and security problems.

Then why not provide one yourself?

No need. There are plenty of other active alternatives

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#15
post #6

I personally treat it as a supply chain risk, as there are no longer any way to report any bugs and security problems.

How is _your_ supply chain a concern of this open source developer?

The parent poster never said it was. They just claimed it's risky for them which I agree with
Post reply on HN