feat(python-sdk): adopt pyqwest 0.8's proxy object, multipart fix, and request loggers

[mishushakov]

What

Tracked in SDK-302 (part of the SDK-268 stack). Stacked on #1623. Adopts the three features merged into pyqwest after 0.7.0 and drops the workarounds the SDK carried while they were missing:

pyqwest PR	What it adds	What it lets us delete here
#194	Proxy object (auth, headers, no_proxy, scheme)	rejecting httpx.Proxy headers; folding credentials into the URL userinfo
#196	multipart form support, and the httpx adapter matching dual sync/async streams sync-first	_SyncOnlyStream, the rewrap of httpx's MultipartStream
#197	pyqwest / pyqwest.access loggers, emitted from Rust at DEBUG	the "until pyqwest ships a logging middleware" note on the RPC interceptor (pyqwest#192 was superseded)

Important

Blocked on a pyqwest 0.8.0 release. All three are on curioswitch/pyqwest@main but unreleased — the latest PyPI release is 0.7.0 (2026-07-19). So uv.lock can't be regenerated and CI's uv sync --locked fails until 0.8.0 is published. Everything below was verified against a wheel built locally from pyqwest@6d56923.

How

Proxy — proxy_to_url() -> Optional[str] becomes proxy_to_config() -> Optional[ProxyConfig], a NamedTuple of (url, auth, headers) that does double duty: it keys the transport caches (a pyqwest.Proxy compares by identity, so caching on one would hand every call its own connection pool) and builds the Proxy via to_pyqwest(). Consequences for the proxy option:

• An httpx.Proxy's custom headers are now honored instead of raising InvalidArgumentException.
• Credentials pass through as a (username, password) pair rather than being percent-encoded back into the URL userinfo — reqwest sends Proxy-Authorization itself.
• A per-proxy ssl_context is still rejected; pyqwest has no counterpart.
• Transports are keyed on the whole config, so the same proxy URL with different credentials or headers gets its own pool.

It's a NamedTuple rather than a frozen dataclass on purpose: tests/test_env_var_parsing.py reloads e2b.api, which rebinds the class, and a dataclass's __eq__ compares class identity — so cache keys created before and after a reload would silently stop matching. Tuples compare by value.

Multipart — ApiPyqwestTransport.handle_request no longer rewraps request streams. httpx's MultipartStream (files= uploads, i.e. files.write) implements both SyncByteStream and AsyncByteStream; the 0.7 adapter matched the async case first and raised TypeError("unreachable") from inside the body iterator, surfacing as a mid-request WriteError. Upstream now matches sync first. The regression test stays and covers the upstream fix.

Loggers — no wiring needed (the loggers are process-wide and emitted from Rust), so this is documentation plus a test that pins the behavior. Two comments record how the layers relate: retrying_http_transport notes that pyqwest logs requests below the SDK's logger option, and LoggingInterceptor's docstring replaces the "stays until pyqwest#192 ships" note — that PR was superseded by #197, whose loggers can't carry a per-sandbox logger nor see streamed messages or the Connect error code of a stream that fails inside a 200 OK, so the interceptor is permanent.

Testing

• Unit suite: 240 passed, 1 skipped. ruff check, ruff format --check, ty check clean.

• New: test_sync_transport_sends_proxy_credentials_and_headers (the echo server stands in for a proxy, asserting absolute-form request target + Proxy-Authorization + the extra header actually reach it) and test_transport_emits_pyqwest_access_log. Rewrote the nine proxy_to_url narrowing tests for proxy_to_config, plus one asserting equal configs share a pool while the Proxy objects they build do not compare equal.

• E2E against production on the local 0.8 wheel, sync and async: create → files.write (single part) → write_files (multi-part body) → file-like write (octet-stream path) → read(format="stream") → commands.run → get_info → kill. All green, with the access log showing every REST, envd, and RPC request:

  DEBUG pyqwest.access - HTTP Request: POST https://api.e2b.app/sandboxes "HTTP/2 201 Created"
  DEBUG pyqwest.access - HTTP Request: POST https://sandbox.e2b.app/files "HTTP/2 200 OK"
  DEBUG pyqwest.access - HTTP Request: POST https://sandbox.e2b.app/process.Process/Start "HTTP/2 200 OK"
  DEBUG pyqwest.access - HTTP Request: DELETE https://api.e2b.app/sandboxes/ickrgvawk1s9mn0963eta "HTTP/2 204 No Content"
  

Usage examples

A proxy that needs a custom header no longer has to be rewritten as a URL — it just works:

import httpx
from e2b import Sandbox

# Previously raised InvalidArgumentException
sbx = Sandbox.create(
    proxy=httpx.Proxy(
        "http://corp-proxy.internal:8030",
        auth=("user", "p@ss"),                 # sent as Proxy-Authorization
        headers={"X-Proxy-Token": "secret"},   # sent to the proxy
    )
)

Transport-level HTTP logs, replacing the httpcore records that the move off httpx transports removed:

import logging

logging.basicConfig()
logging.getLogger("pyqwest.access").setLevel(logging.DEBUG)   # one line per request
logging.getLogger("pyqwest").setLevel(logging.DEBUG)          # + request lifecycle

Sandbox.create()
# DEBUG pyqwest.access - HTTP Request: POST https://api.e2b.app/sandboxes "HTTP/2 201 Created"

Both are opt-in and independent of the SDK's own logger= option, which is unchanged.

Follow-ups

• Rebase note: feat(python-sdk): move the volume content client onto pyqwest #1602 (volume) and feat(python-sdk): move template build-context uploads onto pyqwest #1603 (template uploads) still call proxy_to_url; they need the rename when they rebase onto this.
• Once pyqwest 0.8.0 is out, this can either land as its own commit or be squashed into the stack it corrects — nothing here is a behavior change relative to shipped code, so the changeset edits in feat(python-sdk): move the REST API client onto pyqwest's httpx transport adapter #1601's entry are corrections rather than a new user-visible delta.
• pyqwest 0.8 also brings no_proxy and per-scheme proxy routing, which httpx.Proxy can't express. Not exposed; would need a new SDK option and JS parity.

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: bf0bd6e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@e2b/python-sdk	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cursor]

PR Summary

Medium Risk
Touches shared HTTP/RPC transport and proxy configuration for all API traffic; behavior changes for proxied clients using httpx.Proxy headers, with broad test coverage mitigating regressions.

Overview
Requires pyqwest 0.8 and replaces proxy_to_url with proxy_to_config returning a ProxyConfig NamedTuple (URL, auth, headers) used as transport cache keys and converted via to_pyqwest() for pyqwest transports across REST, envd HTTP, and RPC.

httpx.Proxy custom headers and separate auth credentials are forwarded instead of raising on headers or encoding auth into the URL userinfo; per-proxy ssl_context still raises InvalidArgumentException. Different credentials or headers on the same proxy URL get separate connection pools.

Removes sync ApiPyqwestTransport _SyncOnlyStream rewrap for multipart files= uploads now that pyqwest 0.8 prefers the sync byte stream path. Notes that pyqwest.access / pyqwest DEBUG logging replaces httpcore-style transport diagnostics while the SDK logger option stays on the RPC interceptor. Changesets and tests cover proxy wiring, access logs, and pool caching.

^{Reviewed by Cursor Bugbot for commit bf0bd6e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[linear-code]

SDK-302

[mishushakov]

Superseded: the changes are folded into the stack they correct — the httpx.Proxy → pyqwest.Proxy mapping and the pyqwest 0.8 bump into #1601, the multipart-workaround removal and the envd renames into #1623, and the proxy_to_config rename into #1602/#1603. Tracking stays on SDK-302.