This release is a pre-release and may not be stable for production use.
apache-iggy
Apache Iggy is the persistent message streaming platform written in Rust, supporting QUIC, TCP and HTTP transport protocols, capable of processing millions of messages per second.
Apache Iggy (Incubating) is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Installation
Basic Installation
# Using uv in an existing project
uv add apache-iggy
# Using pip
python3 -m venv .venv
source .venv/bin/activate
pip install apache-iggy
Prerequisites
Every installation below compiles the Rust extension, so you'll need:
- Python 3.10+
- Rust toolchain:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh uv:curl -LsSf https://astral.sh/uv/install.sh | sh- All checks tooling from CONTRIBUTING.md.
- Docker
Local Development
IMPORTANT: All commands are supposed to be ran from foreign/python unless it's specified to run in repository's root folder.
-
Build a project for development
With
uv:# Create a venv uv venv # Sync the environment without updating it uv sync --frozen --all-extras --no-install-project # Build the project -- this builds the rust extension into the venv (debug profile) - re-run after any rust change uv run --no-sync maturin develop
With
pip:# Create a venv python3 -m venv .venv # Activate the venv source .venv/bin/activate # Install the dependencies pip install -e ".[all]" # Build the project -- this builds the rust extension into the venv (debug profile) - re-run after any rust change maturin develop
-
Run the server to be able to run the tests (this blocks the terminal - run steps 3-5 in a separate one).
--freshdeleteslocal_data/on every run - drop it if you have existing data you want to keep.# run from the repository's root directory cargo run --bin iggy-server -- --with-default-root-credentials --fresh
-
Run the tests
uv:uv run --no-sync pytest tests/ -v
pip:pytest tests/ -v # make sure iggy-server is running and the venv is activated
-
To update the stubs, only after changing the pyo3 API surface (nothing in CI checks stub freshness, so unconditional regen just invites
.pyichurn), use# run from foreign/python cargo run --bin stub_gen # TODO: Known bug: running this from a subdirectory of `foreign/python` corrupts the tracked stub, see https://github.com/apache/iggy/pull/3825/changes/BASE..773a27971b4ddb7b44773ded395ed23afb1de4c9#r3727691619
-
Before committing, test the pre-commit and pre-push hooks.
prekonly inspects staged content, so stage your work first:git add -A prek run # runs pre-commit hooks prek run --hook-stage pre-push # if a hook modifies files, re-run `git add -A` and `prek run`.
These are some of the essential commands prek is running, so it's recommended to run them manually before running prek / committing / pushing. This list is not exhaustive and other hook failures are possible.
uv run --no-sync ruff format .
uv run --no-sync ruff check --fix .
cargo fmt --manifest-path Cargo.toml
cargo clippy --manifest-path Cargo.toml --all-targets --all-features -- -D warnings
# run from the repository's root directory ./scripts/ci/markdownlint.sh --fix foreign/python/README.md # read the diff after applying this, sometimes it gives unwanted results, e.g. messing up enumerations
Client Configuration
IggyClient takes either a server address or a TcpConfig:
import asyncio
from datetime import timedelta
from apache_iggy import AutoLogin, IggyClient, TcpConfig, TcpReconnectionConfig
async def main():
client = IggyClient(
TcpConfig(
server_address="127.0.0.1:8090",
auto_login=AutoLogin.username_password("iggy", "iggy"),
reconnection=TcpReconnectionConfig(
enabled=True,
max_retries=10,
interval=timedelta(seconds=2),
reestablish_after=timedelta(seconds=30),
),
heartbeat_interval=timedelta(seconds=5),
# tls_enabled=True,
# tls_domain="localhost",
# tls_ca_file="../../core/certs/iggy_ca_cert.pem",
# tls_validate_certificate=True,
# nodelay=True,
)
)
await client.connect()
asyncio.run(main())
Examples
Refer to the examples/python/ directory for usage examples.
Contributing
See CONTRIBUTING.md for contribution guidelines.
License
Licensed under the Apache License 2.0. See LICENSE for details.
Release files for apache-iggy 0.9.0.dev4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apache_iggy-0.9.0.dev4.tar.gz | 579.9 kB | Details |
Built distributions (wheels)
Total release size: 143.6 MB
Release files / apache_iggy-0.9.0.dev4.tar.gz
| Download URL | apache_iggy-0.9.0.dev4.tar.gz |
|---|---|
| Size | 579.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f82017e3066065574e059cc1bd946a82b6696c3f753279e47a8caeb69647999a
|
|
BLAKE2b-256 checksum How to use checksums |
2b8bcac2e2a40c77f6c2400c21d63d152b4798a0000889a54bc990398532d375
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
fb99c7761676d6518d6c7aed5edbc9156a8a31ae22a12480be44cdaa1ad785cf
|
|
BLAKE2b-256 checksum How to use checksums |
27c6cbda24dcc24854f164b969c3a4ce0183da72d8daf5a9ddeb0e532e39452e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
853fca0f552ec46abe29bf14d810b5022fc2453abaa6c0ec0c03be32f5988e05
|
|
BLAKE2b-256 checksum How to use checksums |
641aa37954c6cdcd5727ee1e68a18e18c1c34f24a0380734fe383d3fe4a00f38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
57cb256819db88682cba63120fee14aec868c700b04433634efc2d9d2502c24d
|
|
BLAKE2b-256 checksum How to use checksums |
ea3adaa0c0153e695a1b6bd0e01c7e290a5ecc146ddbd29bd7c76034a9a963bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
6998aca1d9131869ff8090935892086108be1962cbb7f8e81b091634ec85e105
|
|
BLAKE2b-256 checksum How to use checksums |
ed7ba7e0a00c0557f0a585db6e5d3405da9c55400bc379e491fbf260e4c72d45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0f7bdb16013ea2b4c17b764b20f97c787c6bd8df3c383874ef95fdf51ed44d68
|
|
BLAKE2b-256 checksum How to use checksums |
6c070b14d8ae24f35416aaa0f7b83bb236ab7376e2d4acd10c219f5ba69c2593
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
9155bd415d90a00854b07eee6d03e8abe23d9e02469178f791f7edee574bee8a
|
|
BLAKE2b-256 checksum How to use checksums |
e318690c9da5d33883ff4f8dfd0bad85160a7a63b165d2b21a841dd7373c34c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
e6ab5b3a6b53f256ea56188e9cf0aad0eb57b868a66fe1db755ee19d6479cfba
|
|
BLAKE2b-256 checksum How to use checksums |
e7cda7436de1afe52a039e2e026704dd9a70fbbc0406dbb0753573aa7257e5ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
2abd5c2651898580f3e12dacd4e98c70728c1004cf76932eef896235b96a8177
|
|
BLAKE2b-256 checksum How to use checksums |
7dd49c5a5f729cec1986f240580a9a5bf05a03ffc96074f58f65012696dd3188
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
4e1d33ac57d668a6afce2bd6c212fcc5a9be1de784bdbbca61ac5702a4cc9850
|
|
BLAKE2b-256 checksum How to use checksums |
b0f1335dbf85d3a05fc9025f2cc72caf1da19c6c811dd874224a0222ea36f075
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
b8fd5a2712688eac02168740c47925e8d95b31c64a7ca6a5d8adc5cf990bf705
|
|
BLAKE2b-256 checksum How to use checksums |
075467dbbcefb9e370d9c6f946b73482c2706a92b42819405538fb53b70da6b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9ee35015020f5453c69aefbf25155a33ac8c70b482fcc6a94d054c6884c50ba1
|
|
BLAKE2b-256 checksum How to use checksums |
8f11d5996db037f397ce34225082e6d1b5abb104ca4cff82f5ab03299cbb1c03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
e314e076db1d509a357b70e4304879aa1dbf0177dbea9c630558e1da7a9cd109
|
|
BLAKE2b-256 checksum How to use checksums |
6ba0d29b41f142caf76482b4e20b605ac6ff97749c0c36a49a65679545af7f96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
1d040ebc7942ca9f792c8632a450fcc8701132c45775ba308f985c677347d9e6
|
|
BLAKE2b-256 checksum How to use checksums |
8099e4c53fb3518cc35a18529755d31dc7a7a6a3f0ea3dafbda6bb31934e7b65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
2dce0cf4a02ca7051481648414aee2caa6da216c6da603fc9e01858f49a59996
|
|
BLAKE2b-256 checksum How to use checksums |
eac20f91a4b9d7267746e302e10905368892af0defa92cec58ca9ed7ea7a6620
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
665189b2060d22227ba10a799bf4022512126502cc5b8ca58d1f42c7216f7062
|
|
BLAKE2b-256 checksum How to use checksums |
0a0a4a7d6d6f079501b5af0b7974f09b74dba7e8fde6acf2d19a4df7dbaf2084
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
dc7f0d12c2037cdc2639c4506684d3b0120f9700cefcccde80d9dfd6b5e3724d
|
|
BLAKE2b-256 checksum How to use checksums |
b4f69fc2f19f9404968c5a4525012f1c92079fc810e166eaf5f2c6f0e9372157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b341a177914e035b1ed0104085f45ecf8ddd9a111e5cdb1f7e3ecc2ac87066b8
|
|
BLAKE2b-256 checksum How to use checksums |
caf3bd1778500cb0a354365b5e6c53d4e4f41bfc1d865365349743ea463cc958
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
8372f68813ce10748b6879856b79a4ce837fed1c5c306a605cba8d725df5ed6e
|
|
BLAKE2b-256 checksum How to use checksums |
4f8cd5d213aaf7979a684e03bcbb8f1837f53b7d3bd24752608c6cf6b16cfd83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
67b72a6663ded41f7b8801cb0760cf96e7ba1695bae1439fa2fd9dacbd3d7133
|
|
BLAKE2b-256 checksum How to use checksums |
c56067d5d822aade40f88cc67c96c604433f13a50e4969531182c6815b329381
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp310-cp310-musllinux_1_2_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp310-cp310-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
ebe072e034614e2f5c0c5c7286cfb0ede36542df21b1051d07d8244818fbb427
|
|
BLAKE2b-256 checksum How to use checksums |
f81a61ffb221da1f350e72a769d53a8d01d224c71b6ada625acec3e516c6a851
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp310-cp310-manylinux_2_34_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp310-cp310-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
07cfef70f3d4934037bb7a96d47d5490ac374625d157ca2234ae78d4184c46a0
|
|
BLAKE2b-256 checksum How to use checksums |
6e98c402d060eca3a5b764278a8532b3e58dfd3492c1051dbcfc3143d025d72b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
5392159e7873cd0b773b6a346c90db9103abcd8b557425ec1618f3ef52b4bba1
|
|
BLAKE2b-256 checksum How to use checksums |
2d58e6fce6e58162aead6370c376b44d446b541a0a6b29f9a8f0049b81d3a832
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
936ce76fe26a099bdbea55010b1144703d33975c27b54f145159e7433769c74d
|
|
BLAKE2b-256 checksum How to use checksums |
f4cc3a083f96143dd23491b51ac73cba74843bcb6f6bb9ddbd7aa46705bb3157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency logRelease files / apache_iggy-0.9.0.dev4-cp310-cp310-macosx_10_12_x86_64.whl
| Download URL | apache_iggy-0.9.0.dev4-cp310-cp310-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.10 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
57cbd6960c25dc637d82144daaf542242dedc2c2e85f4fb812ea54940e1879bc
|
|
BLAKE2b-256 checksum How to use checksums |
34c777863382ad323886057f4b13710d8a349f53b44d636878be0fe013372b4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 18, 2026.
Transparency log
