Skip to main content

The zc.lockfile package provides a basic portable implementation of interprocess locks using lock files. The purpose if not specifically to lock files, but to simply provide locks with an implementation based on file-locking primitives. Of course, these locks could be used to mediate access to other files. For example, the ZODB file storage implementation uses file locks to mediate access to file-storage database files. The database files and lock file files are separate files.

Detailed Documentation

Lock file support

The ZODB lock_file module provides support for creating file system locks. These are locks that are implemented with lock files and OS-provided locking facilities. To create a lock, instantiate a LockFile object with a file name:

>>> import zc.lockfile
>>> lock = zc.lockfile.LockFile('lock')

If we try to lock the same name, we’ll get a lock error:

>>> import zope.testing.loggingsupport
>>> handler = zope.testing.loggingsupport.InstalledHandler('zc.lockfile')
>>> try:
...     zc.lockfile.LockFile('lock')
... except zc.lockfile.LockError:
...     print("Can't lock file")
Can't lock file

To release the lock, use it’s close method:

>>> lock.close()

The lock file is not removed. It is left behind:

>>> import os
>>> os.path.exists('lock')
True

Of course, now that we’ve released the lock, we can create it again:

>>> lock = zc.lockfile.LockFile('lock')
>>> lock.close()

Hostname in lock file

In a container environment (e.g. Docker), the PID is typically always identical even if multiple containers are running under the same operating system instance.

Clearly, inspecting lock files doesn’t then help much in debugging. To identify the container which created the lock file, we need information about the container in the lock file. Since Docker uses the container identifier or name as the hostname, this information can be stored in the lock file in addition to or instead of the PID.

Use the content_template keyword argument to LockFile to specify a custom lock file content format:

>>> lock = zc.lockfile.LockFile('lock', content_template='{pid};{hostname}')
>>> lock.close()

If you now inspected the lock file, you would see e.g.:

$ cat lock

123;myhostname

Change History

1.4 (2018-11-12)

  • Claim support for Python 3.6 and 3.7.

  • Drop Python 2.6 and 3.3.

1.3.0 (2018-04-23)

  • Stop logging failure to acquire locks. Clients can do that if they wish.

  • Claim support for Python 3.4 and 3.5.

  • Drop Python 3.2 support because pip no longer supports it.

1.2.1 (2016-06-19)

  • Fixed: unlocking and locking didn’t work when a multiprocessing process was running (and presumably other conditions).

1.2.0 (2016-06-09)

  • Added the ability to include the hostname in the lock file content.

  • Code and ReST markup cosmetics. [alecghica]

1.1.0 (2013-02-12)

  • Added Trove classifiers and made setup.py zest.releaser friendly.

  • Added Python 3.2, 3.3 and PyPy 1.9 support.

  • Removed Python 2.4 and Python 2.5 support.

1.0.2 (2012-12-02)

  • Fixed: the fix included in 1.0.1 caused multiple pids to be written to the lock file

1.0.1 (2012-11-30)

  • Fixed: when there was lock contention, the pid in the lock file was lost.

    Thanks to Daniel Moisset reporting the problem and providing a fix with tests.

  • Added test extra to declare test dependency on zope.testing.

  • Using Python’s doctest module instead of depreacted zope.testing.doctest.

1.0.0 (2008-10-18)

  • Fixed a small bug in error logging.

1.0.0b1 (2007-07-18)

  • Initial release

Metadata

Release files for zc.lockfile 1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zc.lockfile 1.4
File Size Uploaded Provenance Actions
zc.lockfile-1.4.tar.gz 11.1 kB Without provenance Details for zc.lockfile-1.4.tar.gz

Release files / zc.lockfile-1.4.tar.gz

Download URL zc.lockfile-1.4.tar.gz
Size 11.1 kB
Tags Source
SHA-256 checksum
How to use checksums
95a8e3846937ab2991b61703d6e0251d5abb9604e18412e2714e1b90db173253
BLAKE2b-256 checksum
How to use checksums
58c2d7c89bdad237b4b7837609172be3e8bf5630796c0020494a15b97ece8eb1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.10.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.7 CPython/2.7.15

Security for zc.lockfile 1.4

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page