Upstream software project

python-elastic-transport

Transport classes and utilities shared among Python Elastic client libraries

About python-elastic-transport

Transport classes and utilities shared among Python Elastic client libraries

This project links 8 native package records across 6 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-elastic-transport repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 13 (Trixie): 2 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.python-elastic-transport: recorded package coverageDebian 13 (Trixie)2 recordsFedora 431 recordsFedora 441 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-elastic-transport
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, 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.

Transport classes and utilities shared among Python Elastic client libraries This library was lifted from elasticsearch-py and then transformed to be used across all Elastic services rather than only Elasticsearch.

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-elastic-transport

    trixie (Debian 13 (Trixie)) (python): Transport utilities shared by the Elastic client libraries

    8.17.1-2: all

    Source: python-elastic-transport

  2. Package python-elastic-transport-doc

    trixie (Debian 13 (Trixie)) (doc): Transport utilities shared by the Elastic client libraries (Documentation)

    8.17.1-2: all

    Source: python-elastic-transport

Fedora 43

  1. Package python3-elastic-transport

    43 (Fedora 43) (Unspecified): Transport classes and utilities shared among Python Elastic

    9.1.0-2.fc43: noarch

    Source: python-elastic-transport

Fedora 44

  1. Package python3-elastic-transport

    44 (Fedora 44) (Unspecified): Transport classes and utilities shared among Python Elastic

    9.1.0-3.fc44: noarch

    Source: python-elastic-transport

openSUSE Leap 15.6

  1. Package python311-elastic-transport

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Transport classes and utilities shared among Python Elastic client libraries

    8.4.0-150400.9.3.6: noarch

    Source: python-elastic-transport

openSUSE Leap 16.0

  1. Package python313-elastic-transport

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Transport classes and utilities shared among Python Elastic client libraries

    8.17.1-160000.2.2: noarch

    Source: python-elastic-transport

openSUSE Tumbleweed

  1. Package python313-elastic-transport

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Transport classes and utilities shared among Python Elastic client libraries

    9.4.2-2.1: noarch

    Source: python-elastic-transport

  2. Package python314-elastic-transport

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Transport classes and utilities shared among Python Elastic client libraries

    9.4.2-2.1: noarch

    Source: python-elastic-transport

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.