Skip to content

httpxyz/httpx2 support #57

Open
Open

Description

@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

Activity

  1. aiudirog commented on May 11, 2026

    @aiudirog
    Member

    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.

  2. aiudirog commented on May 31, 2026

    @aiudirog
    Member

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

  3. chassing commented on Jun 3, 2026

    @chassing
    Author

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

  4. changed the title [-]httpxyz support[/-] [+]httpxyz/httpx2 support[/+] on Jun 3, 2026
  5. JacobHenner commented on Jun 3, 2026

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

  6. cclauss commented on Sep 17, 2026

    @cclauss
    Contributor

    https://pydantic.dev/docs is a solid home for httpx2 (it is difficult to think of a better place), so are there places where you need help to establish and test compatibility with it?

  7. aiudirog commented on Sep 18, 2026

    @aiudirog
    Member

    Sorry I haven't been actively pushing this forward.

    I guess the important decision is should this package be renamed to httpx2-gssapi to ensure a clean break? While it's possible the APIs will be compatible between the two libraries for at least a while, it could get a bit nasty trying to figure out breakage for users who don't switch their clients down the line.

    I'm also fine with forking this repo and archiving it, leaving the existing package and source frozen. Though we should push one last release to PyPI to add a notice to the README.

  8. cclauss commented on Sep 18, 2026

    @cclauss
    Contributor

    Changing the package name sounds like a lot of work for maintainers of this repo but also for each project that has httpx-gssapi as a dependency. My vote (I am not a maintainer) would be that you keep the current package name and test the two side by side and then when the time is right drop support for legacy httpx.

  9. aiudirog commented on Sep 18, 2026

    @aiudirog
    Member

    Changing the package name sounds like a lot of work for maintainers of this repo but also for each project that has httpx-gssapi as a dependency. My vote (I am not a maintainer) would be that you keep the current package name and test the two side by side and then when the time is right drop support for legacy httpx.

    I'm currently the sole maintainer and it doesn't really matter to me, I'm just looking to avoid headaches for users that could come with dropping the current dependency.

    The biggest problem is that when initializing a client, httpx explicitly checks isinstance(auth, httpx.Auth), which means we can't just inherit from httpx2.Auth and have it be compatible with an httpx.Client.

    So IMO, any way you cut it, you're introducing some sort of backwards incompatible change that downstream has to be aware of:

    • An environment variable to downgrade the backing library like in the proposed PR
      • This requires the user to know to set it and runs into conflicts in complex deployments where dependencies might have differing opinions on which library to use
    • Requiring a user to select the older library when initializing the class
      • Now we're requiring a code change and hot swapping self.__class__ in Auth__init__
    • Dropping httpx support altogether without changing the name
      • Those who aren't pinning the package version will be in for a rude awakening
    • Requiring adoption of a new package name via some find and replace
      • Requires migration but preserves existing behavior for those not pinning packages

    I figure the last option is the most explicit, which does fit with the Zen.

    Regardless, I'm willing to just roll with whatever is most popular/convenient for those actually using this package. So please provide feedback!

    Also, once we've got this ironed out, I plan to jump straight to v2.0 to match httpx2. I was only waiting for v1.0 to match httpx since there were still the occasional breaking changes from upstream.

  10. cclauss commented on Sep 18, 2026

    @cclauss
    Contributor
    try:
        httpx_Auth = httpx2.Auth
    except NameError
        httpx_Auth = httpx.Auth
  11. aiudirog commented on Sep 18, 2026

    @aiudirog
    Member
    try:
        httpx_Auth = httpx2.Auth
    except NameError
        httpx_Auth = httpx.Auth

    That only works if only one is installed... Most users of this package are going to be also listing httpx as a dependency and then if we swap to httpx2 as the required dependency, both will be installed.

  12. cclauss commented on Sep 18, 2026

    @cclauss
    Contributor

    Now I understand. Users would need to bring their own httpx which might break some projects.

  13. sim0nx commented on Sep 23, 2026

    @sim0nx

    I would suggest to rename/fork this repo to httpx2-gssapi for the above mentioned reasons. It also seems cleaner.

  14. aiudirog commented on Sep 28, 2026

    @aiudirog
    Member

    Thanks for the feedback everyone. Once #67 is merged, I'm going to fork this repo to httpx2-gssapi in the same org and continue development from there. Then we'll do one last release here to ensure the docs are updated with a note about the migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions