Upstream software project

python-lockfile

Platform-independent file locking module

About python-lockfile

Platform-independent file locking module

This project links 8 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

python-lockfile repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 2 package records; Fedora 44: 2 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-lockfile: recorded package coverageFedora 432 recordsFedora 442 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-lockfile
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The lockfile package exports a LockFile class which provides a simple API for locking files. Unlike the Windows msvcrt.locking function, the fcntl.lockf and flock functions, and the deprecated posixfile module, the API is identical across both Unix (including Linux and Mac) and Windows platforms. The lock mechanism relies on the atomic nature of the link (on Unix) and mkdir (on Windows) system calls. An implementation based on SQLite is also provided, more as a demonstration of the possibilities it provides than as production-quality code.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package python3-lockfile

    43 (Fedora 43) (Unspecified): Platform-independent file locking module

    1:0.12.2-22.fc43: noarch

    Source: python-lockfile

  2. Package python-lockfile-doc

    43 (Fedora 43) (Unspecified): lockfile documentation

    1:0.12.2-22.fc43: noarch

    Source: python-lockfile

Fedora 44

  1. Package python3-lockfile

    44 (Fedora 44) (Unspecified): Platform-independent file locking module

    1:0.12.2-23.fc44: noarch

    Source: python-lockfile

  2. Package python-lockfile-doc

    44 (Fedora 44) (Unspecified): lockfile documentation

    1:0.12.2-23.fc44: noarch

    Source: python-lockfile

openSUSE Leap 15.6

  1. Package python3-lockfile

    leap-15.6 (openSUSE Leap 15.6) (Development/Languages/Python): Platform-independent file locking module

    0.10.2-2.24: noarch

    Source: python-lockfile

openSUSE Leap 16.0

  1. Package python313-lockfile

    leap-16.0 (openSUSE Leap 16.0) (Development/Languages/Python): Platform-independent file locking module

    0.12.2-bp160.1.12: noarch

    Source: python-lockfile

openSUSE Tumbleweed

  1. Package python313-lockfile

    tumbleweed (openSUSE Tumbleweed) (Development/Languages/Python): Platform-independent file locking module

    0.12.2-4.9: noarch

    Source: python-lockfile

  2. Package python314-lockfile

    tumbleweed (openSUSE Tumbleweed) (Development/Languages/Python): Platform-independent file locking module

    0.12.2-4.9: noarch

    Source: python-lockfile

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.