default to httpx2 and drop support for httpx entirely

[s-sajid-ali]

This PR assumes that the deprecation of generating clients with httpx is imminent and updates all golden records to use httpx2 instead. This leaves the client generation process with legacy httpx untested. This will cause issues when httpx2 introduces breaking changes and it is assumed that the option to use httpx will be removed by that time.

Additionally, this leaves the generated methodget_httpx_client as is, preferring to update it to get_httpx2_client when support for httpx is removed.

[johnthagen]

Related to

• Use the pydantic maintained fork of `httpx`, `httpx2` #1455

[s-sajid-ali]

Split the commit to exclude the changes to pdm.lock file as that was causing merge conflicts and rebased the changes over the current state of main. Let me know if you need anything else!

[johnthagen]

@s-sajid-ali Per discussion here

• Use the pydantic maintained fork of `httpx`, `httpx2` #1455 (reply in thread)

Would you be willing to modify this PR to target only httpx2? We can skip the complexities of trying to support both given the way the community is moving.

[s-sajid-ali]

Sure, it should be much easier to move everything over to httpx2 and not support both. I'll get the change in place by the middle of the upcoming week.

[s-sajid-ali]

Updated to only use httpx2 and ready for another review.

This now includes breaking API changes as noted in the changeset:

• set_httpx_client -> set_httpx2_client
• get_httpx_client -> get_httpx2_client
• set_async_httpx_client -> set_async_httpx2_client
• get_async_httpx_client -> get_async_httpx2_client

Since this is a major version change that breaks with httpx, I'm assuming that this API change is acceptable. If not, these APIs can be kept as is.

[johnthagen]

I think migrating to *_httpx2_client function names makes sense. It's probably safer to be explicit about this and it's nicer longer term. This change can be easily detected by type checkers and IDEs, so hopefully that makes the migration straight forward.

[johnthagen]

CI failures need fixed.

[s-sajid-ali]

CI needs permission to re-run but format checks are now clean:

~/D/p/openapi-python-client (httpx-switch-default-to-2)> git log -n 1
commit cd3b41cb0aeec512779f34c6763f79ee1254d3d4 (HEAD -> httpx-switch-default-to-2, origin/httpx-switch-default-to-2)
Author: Sajid Ali <sajidsyed2021@u.northwestern.edu>
Date:   Tue Sep 22 19:43:01 2026 -0400

    ruff format in integration-tests/ to fix formatting error from CI
~/D/p/openapi-python-client (httpx-switch-default-to-2)> pdm run ruff format . --check
130 files already formatted

[johnthagen]

Since this isn't merged yet, perhaps we bump the minimum version to 2.13.1 that was just released

• https://github.com/pydantic/httpx2/releases/tag/v2.13.1

[s-sajid-ali]

Updated to 2.13.1 as requested and I see that the CI failures from the last run are unrelated to this branch, with the following being a representative failure:

PLR0917 Too many positional arguments (8 > 5)
  --> tests/test_parser/test_properties/test_union.py:34:5
   |
34 | def test_union_oneOf_descriptive_type_name(
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
35 |     union_property_factory,
36 |     date_time_property_factory,
   |

This would be best addressed in a separate PR with two commits capturing the changes from:

pdm ruff check --fix .

and

pdm ruff check --fix --unsafe-fixes .

with a review focused on the changes introduced by the second commit.