Option not to raise when leaving context manager after lock expiration · Issue #3532 · redis/redis-py (original) (raw)
Navigation Menu
- Explore
- Pricing
Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Description
Description
I was having trouble using async locks with the context manager because it was failing when exiting the context manager after timeout had expired (even if my code executed successfully).
I would really like not to raise a LockNotOwnedError in the exit of the context manager (if I try to release a lock and it was already "released" then great!).
I understand just changing the behavior would be critical, so I added an option to just behave this way when desired instead.
PR: #3531