OpenAI SDK for Python 3.8

Apply the Python 3 baseline first, then these rules for code that calls the OpenAI API through the openai package on the 3.8 line. The 3.x line moved the default HTTP stack to HTTPX2, so verify transport, trust-store, and redirect assumptions carried over from a 2.x integration before shipping.

Version scope and dependencies

• Pin openai to an exact release in the lockfile and review the changelog before moving the pin, because the SDK's frequent minor releases add authentication and tool surfaces.
• Use CPython 3.11 through 3.14 for this SDK line; its declared requires-python >= 3.10 also permits the end-of-life 3.10 runtime and is not a security-support check.
• Verify the locked SDK and its dependencies before adopting CPython 3.15: it is a stable runtime, but the 3.8 SDK's compatibility matrix still marks it as an allowed failure.
• Install only the extras the service actually uses, because realtime, aiohttp, datalib, voice_helpers, and bedrock each pull additional runtime dependencies into the image.
• Keep pydantic on a maintained 2.x release; the SDK still accepts 1.10.13 or later, but the parsing helpers and strict tool schemas are exercised against Pydantic 2.
• Do not install the legacy httpx escape-hatch client unless a specific transport or mocking dependency forces it; it is runtime-only, defeats static typing, and the project may discontinue it.

Client construction and credentials

• Construct an explicit OpenAI or AsyncOpenAI instance per configuration instead of relying on the legacy module-level client, whose provider