Httpx closing down issues and discussions due to "skewed gender representation" (opens in new tab)

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

That's the totality of the message.

Weirdly enough, the concept of "an environment I don't personally find welcoming is unwelcoming — and better gone" strikes me as rather unwelcoming and indicative of a diet in severe need of iron-y supplementation.

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

Leaves some broken links on their contributing page: https://www.python-httpx.org/contributing/

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

absurdly skewed gender representation, actually! :)