Releases: austind/retryhttp
Releases · austind/retryhttp
v1.4.0
v1.3.3
v1.3.2
Release v1.3.1
- Resolves all outstanding mypy errors (#20)
v1.3.0
- #15: Fix typing error
- Add default fallback wait strategy [tenacity.wait_random_exponential][] to retryhttp.wait_from_header and retryhttp.wait_retry_after (#17)
v1.2.0
- Added
wait_maxargument toretryhttp.wait_from_headerandretryhttp.wait_retry_after, which defaults to 120.0 seconds. retryhttp._utils.is_rate_limited: revert behavior to correctly determine rate limiting by a429 Too Many Requests` status.- When receiving
503 Service Unavailable, honor aRetry-Afterheader if provided. - Rename
retryhttp.wait_rate_limitedtoretryhttp.wait_retry_after, but retain alias for backwards compatibility and convenience. retryhttp.wait_from_header: Handle case if server responds with a date in the past.retryhttp.wait_context_aware: Thewait_server_errorsargument now defaults toretryhttp.wait_retry_afterwithtenacity.wait_random_exponential as fallback, since some server errors may respond with aRetry-After` header.retryhttp.wait_context_aware: Thewait_rate_limitedargument now hastenacity.wait_random_exponentialas fallback toretryhttp.wait_retry_after, to make retrying rate-limited requests more robust.
v1.1.0
- Add HTTP-date value parsing for
retryhttp.wait_from_header retryhttp._utils.is_rate_limitednow determines that a request was rate limited by the presence of aRetry-Afterheader. In prior versions, this was based on the status code429 Too Many Requests. However, many servers return other status codes when rate limiting.
v1.0.1
- FIx documentation errors.
v1.0.0
v0.2.0
- Rename
retryhttp.retry_http_errorstoretryhttp.retry. - Rename
retryhttp.wait_http_errorstoretryhttp.wait_context_aware. - Restructure project so all members are part of the root namespace.
- Move type delcarations to
retryhttp._types. - Enable bare decorator syntax for
retryhttp.retry(i.e.,@retryworks as well as@retry())