pico-resilience 0.1.0

Resilience AOP for the Pico ecosystem: @retryable, @circuit_breaker and @timeout method interceptors.

📦 pico-resilience

Spring-style resilience annotations for the Pico ecosystem, built on pico-ioc method interception and auto-discovered by pico-boot. Zero-config.

Decorator	Policy
@retryable(max_attempts, backoff_seconds, retry_on)	Exponential-backoff retry (sync + async)
@circuit_breaker(failure_threshold, reset_timeout_seconds)	Per-method circuit: closed → open → half-open
@timeout(seconds)	Async time budget via asyncio.timeout

Install

pip install pico-resilience

Use

from pico_ioc import component
from pico_resilience import retryable, circuit_breaker, timeout

@component
class PaymentGateway:
    @retryable(max_attempts=3, backoff_seconds=0.2, retry_on=(ConnectionError,))
    @circuit_breaker(failure_threshold=5, reset_timeout_seconds=30)
    def charge(self, order): ...

    @timeout(2.0)
    async def query_partner(self, q): ...

Failures raise RetryExhaustedError / CircuitOpenError / TimeoutError with the method name. resilience.enabled: false in application.yaml bypasses every policy (handy in tests).

Chain rule: put @retryable at the top when combining decorators (it runs innermost); @circuit_breaker/@cacheable below it then wrap the whole retry loop — the circuit counts exhausted retries and the cache stores the final result. @timeout rejects sync methods at import time: a thread cannot be cancelled, and a timeout that lies is worse than none.

Documentation

Full docs at dperezcabrera.github.io/pico-resilience.

License

MIT