Upstream software project

python-persistent

Translucent persistent objects

About python-persistent

Translucent persistent objects

This project links 12 native package records across 4 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-persistent repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 13 (Trixie): 2 package records; openSUSE Leap 15.6: 4 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.python-persistent: recorded package coverageDebian 13 (Trixie)2 recordsopenSUSE Leap 15.64 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-persistent
Publisher
Not authoritatively mapped
Native package records
12
Operating systems
debian-13, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
ZPL-2.1
Source repository
Open source repository

Source-reported description

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

This package contains a generic persistence implementation for Python. It forms the core protocol for making objects interact "transparently" with a database such as the ZODB.

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.

Debian 13 (Trixie)

  1. Package python3-persistent

    trixie (Debian 13 (Trixie)) (python): Automatic persistence for Python objects

    6.1.1-1: amd64 arm64

    Source: python-persistent

  2. Package python-persistent-doc

    trixie (Debian 13 (Trixie)) (doc): Automatic persistence for Python objects - documentation

    6.1.1-1: all

    Source: python-persistent

openSUSE Leap 15.6

  1. Package python311-persistent

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Translucent persistent objects

    5.1-bp156.1.1: aarch64 ppc64le s390x x86_64

    Source: python-persistent

  2. Package python311-persistent-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Translucent persistent objects

    5.1-bp156.1.1: aarch64 ppc64le s390x x86_64

    Source: python-persistent

  3. Package python3-persistent

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Translucent persistent objects

    4.7.0-bp156.1.1: aarch64 ppc64le s390x x86_64

    Source: python3-persistent

  4. Package python3-persistent-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Translucent persistent objects

    4.7.0-bp156.1.1: aarch64 ppc64le s390x x86_64

    Source: python3-persistent

openSUSE Leap 16.0

  1. Package python313-persistent

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Translucent persistent objects

    5.2-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: python-persistent

  2. Package python313-persistent-devel

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Translucent persistent objects

    5.2-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: python-persistent

openSUSE Tumbleweed

  1. Package python313-persistent

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Translucent persistent objects

    6.8-1.1: x86_64

    Source: python-persistent

  2. Source: python-persistent

  3. Package python314-persistent

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Translucent persistent objects

    6.8-1.1: x86_64

    Source: python-persistent

  4. Source: python-persistent

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.