-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Standardize timeout values to floats in seconds #1747
Copy link
Copy link
Closed
Labels
P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featurebreaking changeWill break existing deployments when updated without changesWill break existing deployments when updated without changesenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedv2Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixesIdeas, requests and plans for v2 of the SDK which will incorporate major changes and fixes
Metadata
Metadata
Assignees
Labels
P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featurebreaking changeWill break existing deployments when updated without changesWill break existing deployments when updated without changesenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedv2Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixesIdeas, requests and plans for v2 of the SDK which will incorporate major changes and fixes
Summary
Standardize all timeout parameters across the SDK to use floats representing seconds, following Python ecosystem conventions.
Problem
Timeout values in the SDK may use inconsistent units or types across different modules. The Python ecosystem (stdlib, httpx, starlette) consistently uses floats representing seconds for timeouts.
Goal
floattype representing secondsAI Disclaimer