Yeah, so with #httpx being forked into httpx2, different projects are adapting different strategies. Some are straightaway replacing httpx with httpx2. Others support both. Even others are rebuilt or forked against httpx2.
So someone decided to build pytest-httpx2 which is a httpx2 hack over respx. Except that respx still requires httpx, so you effectively pull both httpx and httpx2 as a result.
Then someone decided they want a plain fork of pytest-httpx for httpx2. But since pytest-httpx2 was taken, the "obvious" thing to do was to make httpx2-pytest.
Obviously there's zero confusion to be had here.
https://pypi.org/project/pytest-httpx2/
https://pypi.org/project/httpx2-pytest/
