Upstream software project

python-requirements-parser

Pip requirement file parser

About python-requirements-parser

Pip requirement file parser

This project links 2 native package records across 1 recorded operating-system release. 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-requirements-parser repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-requirements-parser: recorded package coverageopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-requirements-parser
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

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

A Pip requirement file parser.

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.

openSUSE Tumbleweed

  1. Package python313-requirements-parser

    tumbleweed (openSUSE Tumbleweed) (Development/Languages/Python): Pip requirement file parser

    0.13.0-1.2: noarch

    Source: python-requirements-parser

  2. Package python314-requirements-parser

    tumbleweed (openSUSE Tumbleweed) (Development/Languages/Python): Pip requirement file parser

    0.13.0-1.2: noarch

    Source: python-requirements-parser

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.