httpxyz support

[mbeijen]

Hi, I am Michiel and I'm one of the maintainers of httpxyz

See https://tildeweb.nl/~michiel/httpxyz.html

Thinking out loud, if someone who has a codebase that uses pytest_httpx and httpx would like to switch to httpxyz, how would you approach that? httpxyz is api-compatible, and we have 'import magic' that registers it as httpx if you first import httpxyz.

Would you have any thoughts? I think creating pytest_httpxyz would not be ideal

[Colin-b]

I was not aware that httpx was forked already, you make valid points in the decision to fork.
I assume pytest plugin loading is importing our init, which in turns import httpx.
If this prevents the proper usage of httpxyz, we could always foresee a import statement in a try/except ImportError block to add compatibility, if there is no other way around it. I would have to check pytest documentation a bit more to see if there is no way around that.

[mbeijen]

thanks for your swift reply and your encouraging words!

I now added and documented this workaround: https://httpxyz.org/httpx-compatibility/#using-pytest-httpx-in-pytest -- for me that works but it's not super pretty

[Owen-OptiGrid]

I have the same question - but for the pydantic httpx2 fork instead.

[angryfoxx]

i think we have to fork this repo for our purposes like pytest_httpxyz, pytest_httpx2.
because in future there can be multiple httpx fork and we may not know which repo corresponds to which httpx fork, so this repo should represent original version and then people can differ and use what they want

[angryfoxx]

btw i created https://github.com/angryfoxx/httpx2-pytest
this package fully comptable with httpx2 and pytest_httpx

also there is another option Erik Lundberg's pytest-httpx2 , built on respx. It is not a drop-in replacement for pytest-httpx the API and configuration differ from Colin’s plugin.