Add pyresilience#3209
Open
AhsanSheraz wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Satoshi nakamoto just woke up |
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
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.
Project
pyresilience
Checklist
Add project-name- [project-name](url) - Description ending with period.Why This Project Is Awesome
Which criterion does it meet? (pick one)
Explain:
pyresilience unifies seven fault-tolerance patterns (retry, circuit breaker, timeout, fallback, bulkhead, rate limiter, and cache) behind a single
@resilient()decorator, with zero external dependencies and native async/await support.Justification for Hidden Gem despite 54 stars (below the preferred 100–500 range):
How It Differs
The list currently has no fault-tolerance / resilience entry (no
tenacity, no circuit-breaker library), so this is added under a new Resilience section in the DevOps group. Unlike single-purpose retry libraries, pyresilience coordinates multiple patterns together — e.g. circuit-breaker state influences retry behavior — and works transparently for both sync and async functions.