Skip to content
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

Merged
merged 6 commits into from
May 13, 2022

Conversation

myheroyuki
Copy link
Contributor

Addresses issue #57

@jugmac00
Copy link
Member

jugmac00 commented May 3, 2022

There is a typo in ImmediateAquireError - I think this should be ImmediateAcquireError

Copy link
Collaborator

@FFY00 FFY00 left a 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

@myheroyuki
Copy link
Contributor Author

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.

@jugmac00
Copy link
Member

jugmac00 commented May 4, 2022

There is one flake 8 issue.

src/filelock/_api.py Outdated Show resolved Hide resolved
@gaborbernat
Copy link
Member

You'll need to fix the CI 👍

@gaborbernat gaborbernat merged commit 4555608 into tox-dev:main May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants