Feature/devexp 1394 python support http 429 with without retry after header#159
Merged
marcos-sinch merged 9 commits intoJun 24, 2026
Conversation
marcos-sinch
requested review from
Hurus111,
JPPortier,
asein-sinch,
edu-sinch and
matsk-sinch
as code owners
JPPortier
reviewed
Jun 24, 2026
JPPortier
previously approved these changes
Jun 24, 2026
JPPortier
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support HTTP 429 retries (with and without
Retry-Afterheader)Adds automatic retries for rate-limited (429) responses in
HTTPTransport, applied on both the normal and legacy paths and after token renewal. Retries are opt-in per endpoint: only endpoints that set HTTPEndpoint.IS_RETRYABLE = True are retried (False by default), so existing endpoints keep their current behaviour. Currently only OAuthEndpoint retries._send_with_retriesretries up toMAX_RETRIES, if exhausted, it returns the last response to the caller.Retry-Afterheader when present (seconds or HTTP date), otherwise it uses exponential backoff with full jitter.