OpenAI Python SDK switches default HTTP client to HTTPX2
OpenAI has updated its Python SDK to use HTTPX2 instead of HTTPX for both synchronous and asynchronous HTTP clients, with HTTPX2 now installed automatically alongside the openai package. Existing API calls, streaming, retries and timeout settings keep working without code changes, but the SDK no longer installs the httpx or certifi packages by default.
GoKawiil's interpretation of the reporting above, not reported fact.
The switch to relying on the operating system's certificate trust store instead of certifi's bundled CA list can silently break TLS verification in minimal containers, corporate proxy setups, or systems with custom certificate bundles. Developers who previously depended on httpx being installed transitively must now add it explicitly, and teams using OpenAI's SDK in production should audit their environments' CA certificate configuration before upgrading.
- OpenAI's Python SDK now uses HTTPX2 as its default HTTP client, replacing HTTPX.
- HTTPX2 verifies TLS certificates using the OS trust store rather than certifi, which can break deployments in minimal containers or proxy environments.
- Developers can set SSL_CERT_FILE or SSL_CERT_DIR, or pass a custom ssl.SSLContext, to control certificate verification explicitly.
Source: github.com, 2026-08-28
Published there as: “OpenAI: Migrating to HTTPX2”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.