httpxyz/httpx2 support

[chassing]

Could you please add support for the httpxyz? So far as I understood, httpx is no longer maintained :(

TBH, I don't know how to achieve that without a breaking change, e.g., via:

[options]
install_requires =
    gssapi

[options.extras_require]
httpx = httpx>=0.16,<0.29
httpxyz = httpxyz>=0.31

[aiudirog]

Yeah this is a tricky one.

I've been following the situation and not really sure where things are going. Like they highlighted in your link, who knows how long their fork will survive and I've been looking at niquests as well, which looks to solve almost all of the other problems I've run into with httpx. Specifically the issue about connection errors under load hit my team very hard and we had to switch to other libraries that didn't need gasapi.

Maybe the best solution is to fork this repo and do a find & replace for httpxyz in the meantime? Doesn't really scale that well though if projects come and go.

[aiudirog]

@JacobHenner are you still actively using this package? You've previously been on top of new HTTPX releases, so I'm curious what your current plans are.

[chassing]

Looks like the community is moving towards httpx2. What do you think about a breaking change and switch to httpx2 for httpx-gssapi?

[JacobHenner]

@JacobHenner are you still actively using this package? You've previously been on top of new HTTPX releases, so I'm curious what your current plans are.

Yes, my organization is still using this package.

I've been following the situation and not really sure where things are going. Like they highlighted in your link, who knows how long their fork will survive and I've been looking at niquests as well, which looks to solve almost all of the other problems I've run into with httpx. Specifically the issue about connection errors under load hit my team very hard and we had to switch to other libraries that didn't need gasapi.

This is similar to our experience. We've been following the situation with httpx, and my personal interpretation is not optimistic. While httpnext was still around I noted parallels between requests/requests3 and httpx/httpnext, and it does appear like httpnext met the same fate and was abandoned. We also were affected by connection errors under load, but we still very much require gssapi support.

Looks like the community is moving towards httpx2. What do you think about a breaking change and switch to httpx2 for httpx-gssapi?

We initially swapped our projects over to httpxyz, but this blog post from the httpxyz maintainer suggests the httpx2 fork should be viewed as the 'blessed' one. I agree with the thoughts expressed in that post.