Locket implements a file-based lock that can be used by multiple processes provided they use the same path.
import locket
# Wait for lock
with locket.lock_file("path/to/lock/file"):
perform_action()
# Raise LockError if lock cannot be acquired immediately
with locket.lock_file("path/to/lock/file", timeout=0):
perform_action()
# Raise LockError if lock cannot be acquired after thirty seconds
with locket.lock_file("path/to/lock/file", timeout=30):
perform_action()
# Without context managers:
lock = locket.lock_file("path/to/lock/file")
try:
lock.acquire()
perform_action()
finally:
lock.release()
Locks largely behave as (non-reentrant) Lock instances from the threading module in the standard library. Specifically, their behaviour is:
Locks are uniquely identified by the file being locked, both in the same process and across different processes.
Locks are either in a locked or unlocked state.
When the lock is unlocked, calling acquire() returns immediately and changes the lock state to locked.
When the lock is locked, calling acquire() will block until the lock state changes to unlocked, or until the timeout expires.
If a process holds a lock, any thread in that process can call release() to change the state to unlocked.
Calling release() on an unlocked lock raises LockError.
Behaviour of locks after fork is undefined.
Installation
pip install locket
Metadata
Release files for locket 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| locket-1.0.0.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| locket-1.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / locket-1.0.0.tar.gz
| Download URL | locket-1.0.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c0d4c052a8bbbf750e056a8e65ccd309086f4f0f18a2eac306a8dfa4112a632
|
|
BLAKE2b-256 checksum How to use checksums |
2f8397b29fe05cb6ae28d2dbd30b81e2e402a3eed5f460c26e9eaa5895ceacf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.2
|
Release files / locket-1.0.0-py2.py3-none-any.whl
| Download URL | locket-1.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b6c819a722f7b6bd955b80781788e4a66a55628b858d347536b7e81325a3a5e3
|
|
BLAKE2b-256 checksum How to use checksums |
dbbc83e112abc66cd466c6b83f99118035867cecd41802f8d044638aa78a106e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.2
|
Security for locket 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.