Upstream software project

pyproject-metadata

PEP 621 metadata parsing

About pyproject-metadata

PEP 621 metadata parsing

This project links 13 native package records across 9 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

pyproject-metadata repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Alpine Linux 3.21: 2 package records; Alpine Linux 3.22: 2 package records; Alpine Linux 3.23: 2 package records; Debian 12 (Bookworm): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 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.pyproject-metadata: recorded package coverageAlpine Linux 3.212 recordsAlpine Linux 3.222 recordsAlpine Linux 3.232 recordsDebian 12 (Bookworm)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 records
OpenFactory diagram of linked package records. The first eight releases are shown; all 9 appear below. It is not an application screenshot.

Project identity

Project
pyproject-metadata
Publisher
Not authoritatively mapped
Native package records
13
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, debian-12, 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.

Dataclass for PEP 621 metadata with support for core metadata generation This project does not implement the parsing of `pyproject.toml` containing PEP 621 metadata. Instead, given a Python data structure representing PEP 621 metadata (already parsed), it will validate this input and generate a PEP 643-compliant metadata file (e.g. `PKG-INFO`).

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.

Alpine Linux 3.21

  1. Source: py3-pyproject-metadata

  2. Package py3-pyproject-metadata-pyc

    v3.21 (Alpine Linux 3.21): Precompiled Python bytecode for py3-pyproject-metadata

    0.9.0-r0: aarch64 x86_64

    Source: py3-pyproject-metadata

Alpine Linux 3.22

  1. Source: py3-pyproject-metadata

  2. Package py3-pyproject-metadata-pyc

    v3.22 (Alpine Linux 3.22): Precompiled Python bytecode for py3-pyproject-metadata

    0.9.1-r0: aarch64 x86_64

    Source: py3-pyproject-metadata

Alpine Linux 3.23

  1. Source: py3-pyproject-metadata

  2. Package py3-pyproject-metadata-pyc

    v3.23 (Alpine Linux 3.23): Precompiled Python bytecode for py3-pyproject-metadata

    0.9.1-r0: aarch64 x86_64

    Source: py3-pyproject-metadata

Debian 12 (Bookworm)

  1. Package python3-pyproject-metadata

    bookworm (Debian 12 (Bookworm)) (python): Dataclass for PEP 621 metadata with support for [core metadata] generation

    0.6.1-3: all

    Source: pyproject-metadata

Fedora 43

  1. Source: python-pyproject-metadata

Fedora 44

  1. Source: python-pyproject-metadata

openSUSE Leap 15.6

  1. Source: python-pyproject-metadata

openSUSE Leap 16.0

  1. Source: python-pyproject-metadata

openSUSE Tumbleweed

  1. Source: python-pyproject-metadata

  2. Source: python-pyproject-metadata

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.