Upstream software project

python-zeep

A Python SOAP client based on lxml/requests

About python-zeep

A Python SOAP client based on lxml/requests

This project links 3 native package records across 2 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

openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-zeep: recorded package coverageopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-zeep
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
opensuse-leap-15-6, opensuse-tumbleweed
License expression
MIT
Source repository
Not reported

Source-reported description

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

Python SOAP client based on python-lxml and python-requests

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 Leap 15.6

  1. Package python3-zeep

    leap-15.6 (openSUSE Leap 15.6) (Development/Languages/Python): A Python SOAP client based on lxml/requests

    3.4.0-bp156.3.2: noarch

    Source: python-zeep

openSUSE Tumbleweed

  1. Package python313-zeep

    tumbleweed (openSUSE Tumbleweed) (Unspecified): A Python SOAP client based on lxml/requests

    4.3.3-1.2: noarch

    Source: python-zeep

  2. Package python314-zeep

    tumbleweed (openSUSE Tumbleweed) (Unspecified): A Python SOAP client based on lxml/requests

    4.3.3-1.2: noarch

    Source: python-zeep

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.