Skip to content

Use vws-python's own HTTPX2 transports in the tests - #3566

Merged
adamtheturtle merged 1 commit into
mainfrom
adamtheturtle/fix-issue-3546
Sep 7, 2026
Merged

Use vws-python's own HTTPX2 transports in the tests#3566
adamtheturtle merged 1 commit into
mainfrom
adamtheturtle/fix-issue-3546

Conversation

@adamtheturtle

@adamtheturtle adamtheturtle commented Sep 7, 2026

Copy link
Copy Markdown
Member

Closes #3546.

vws-python 2026.09.07 (released today, from VWS-Python/vws-python#3195) ships HTTPX2Transport and AsyncHTTPX2Transport.

  • Bump the vws-python dev pin to 2026.9.7.
  • Delete the stand-in tests/mock_vws/utils/httpx2_transports.py.
  • Import the released transports from vws.transports in tests/mock_vws/test_httpx2_mock_usage.py. The test bodies are unchanged.

No HTTPX2 transport implementation remains in this repository. No newsfragment, as this is a test-only change plus a dev dependency bump.

🤖 Generated with Claude Code

@adamtheturtle @claude
Use vws-python's own HTTPX2 transports in the tests
2c8a3d4 
vws-python 2026.09.07 ships HTTPX2Transport and AsyncHTTPX2Transport, so
the stand-in transports which lived in tests/mock_vws/utils are no longer
needed. The HTTPX2 mock usage tests now drive the vws-python clients
through the released transports.

Closes #3546

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Use vws-python's own HTTPX2 transports in the tests, in place of the stand-ins

1 participant

@adamtheturtle