NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #4506 most downloaded on PyPI
Retry potentially transient HTTP errors in Python.
Last release 3 months ago
22 Jun 2026
Release timing varies
gaps range from 2 weeks to 8 months
Nearly every release is documented
notes for 12 of 12 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
12 releases · first in 2024
Added support for httpx2 ( #32 ).
httpx2 (#32).Dropped support for Python 3.8, added support for Python 3.13
One column per month.
Bugfix: Pass error types to wait strategy in retry decorator
Bugfix: Don't pass stop, wait, and retry keyword arguments from retryhttp.retry() on to tenacity.retry()
stop, wait, and retry keyword arguments from retryhttp.retry() on to tenacity.retry() (#23)Resolves all outstanding mypy errors
Add default fallback wait strategy [tenacity.wait_random_exponential][] to retryhttp.wait_from_header and retryhttp.wait_retry_after
Added wait_max argument to retryhttp.wait_from_header and retryhttp.wait_retry_after, which defaults to 120.0 seconds.
wait_max argument to retryhttp.wait_from_header and retryhttp.wait_retry_after, which defaults to 120.0 seconds.retryhttp._utils.is_rate_limited: revert behavior to correctly determine rate limiting by a 429 Too Many Requests` status.503 Service Unavailable, honor a Retry-After header if provided.retryhttp.wait_rate_limited to retryhttp.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: The wait_server_errors argument now defaults to retryhttp.wait_retry_after with tenacity.wait_random_exponential as fallback, since some server errors may respond with a Retry-After` header.retryhttp.wait_context_aware: The wait_rate_limited argument now has tenacity.wait_random_exponential as fallback to retryhttp.wait_retry_after, to make retrying rate-limited requests more robust.Add HTTP-date value parsing for retryhttp.wait_from_header
retryhttp.wait_from_headerretryhttp._utils.is_rate_limited now determines that a request was rate limited by the presence of a Retry-After header. In prior versions, this was based on the status code 429 Too Many Requests. However, many servers return other status codes when rate limiting.FIx documentation errors.
API is now stable. Any breaking changes will follow SemVer guidelines.
requests.exceptions.ChunkedEncodingError to the list of default network errors.Rename retryhttp.retry_http_errors to retryhttp.retry.
retryhttp.retry_http_errors to retryhttp.retry.retryhttp.wait_http_errors to retryhttp.wait_context_aware.retryhttp._types.retryhttp.retry (i.e., @retry works as well as @retry())Added the following methods and classes:
Initial release.
Added the following methods and classes:
retryhttp.retry_http_errorsretryhttp.retry_if_network_error][]retryhttp.retry_if_rate_limited][]retryhttp.retry_if_server_error][]retryhttp.retry_if_timeout][]retryhttp.wait_from_header][]retryhttp.wait_rate_limited][]retryhttp.wait_context_aware][]Your coding agent can read these notes before it upgrades. Set up the MCP server →