-
-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to return immediately when a lock cannot be obtained inst… #142
Add ability to return immediately when a lock cannot be obtained inst… #142
Conversation
There is a typo in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't blocking
/nonblocking
be a more standard name?
Eg. https://docs.python.org/3/library/threading.html#threading.Lock.acquire
…dard name blocking
I chose return_immediately because it was suggested in the original issue, but I agree blocking/nonblocking is the more standard convention. I updated the PR to change to blocking. |
There is one flake 8 issue. |
You'll need to fix the CI 👍 |
Addresses issue #57