fizzpy
A small TLS 1.3 HTTP client for Python, built on Facebook's Fizz (C++) via pybind11.
By default it offers a post-quantum key exchange — the standardized hybrid
X25519MLKEM768 group (codepoint 4588). An ordinary GET negotiates a hybrid
ML-KEM handshake against servers that support it (Cloudflare, Google) and falls
back to classical X25519 against those that don't.
TLS 1.3 only, HTTP/1.1 only. This is a focused toolkit / learning project, not a drop-in
requestsreplacement. See Status.
A fizzpy request captured in Wireshark: the TLS 1.3 ClientHello offers the
post-quantum X25519MLKEM768 group (0x11ec), and a custom marker extension
(0xFE5A, see below) makes it unmistakably
ours — generated by examples/pq_marker.py.
Install
pip install fizzpy
The Linux wheels are self-contained: folly, Fizz, and liboqs are statically
linked into the extension, so a fresh pip install has working post-quantum
TLS with no system packages to add. certifi (pulled in automatically) supplies
the default trust store.
Wheels are produced by CI (manylinux_2_28, x86_64, CPython 3.10–3.14); if one
isn't available for your platform yet, build from source — see
BUILDING.md.
Usage
Synchronous:
import fizzpy
r = fizzpy.get("https://www.cloudflare.com")
print(r.status_code) # 200
print(r.headers["content-type"]) # text/html; charset=UTF-8
print(r.text[:64])
# The negotiated TLS 1.3 parameters are attached to every response:
print(r.tls)
# {'version': 'TLSv1.3', 'cipher': 'TLS_AES_128_GCM_SHA256',
# 'group': 'X25519MLKEM768', 'group_code': 4588,
# 'alpn': 'http/1.1', 'sni': 'www.cloudflare.com', 'peer_cert': '...'}
Asynchronous (the same C++ core, resolved on the running event loop):
import asyncio
from fizzpy.aio import AsyncClient
async def main():
async with AsyncClient() as client:
r = await client.get("https://www.google.com")
print(r.status_code, r.tls["group"], r.tls["group_code"])
asyncio.run(main())
Choosing the key exchange
The default offers [x25519_mlkem768, x25519], mirroring how Chrome and Firefox
send both key shares. Override it per client:
import fizzpy
from fizzpy import NamedGroup
# Force post-quantum only (handshake fails if the server lacks ML-KEM):
pq = fizzpy.Client(groups=[NamedGroup.x25519_mlkem768])
# Classical only:
classical = fizzpy.Client(groups=[NamedGroup.x25519])
Custom ClientHello extensions
fizzpy surfaces Fizz's low-level extension hook, so you can append arbitrary
extensions to the TLS 1.3 ClientHello. Each is an opaque (type, data) pair;
fizzpy rejects types it manages itself (key_share, supported_versions, …) and
out-of-range or duplicate types.
import fizzpy
client = fizzpy.Client(
extensions=[fizzpy.Extension(0xFE5A, b"hello from fizzpy")],
)
r = client.get("https://blog.cloudflare.com")
print(r.tls["group"]) # still negotiates X25519MLKEM768
The extension is sent verbatim in the ClientHello — see it on the wire with
examples/pq_marker.py and the screenshot above.
Certificate verification
Certificate chains are verified against the certifi CA bundle and the hostname is checked against the certificate's SAN by default. Point at a custom CA, or disable verification entirely:
fizzpy.Client(cafile="/path/to/ca.pem") # trust a specific CA
fizzpy.Client(verify=False) # accept any certificate (insecure)
Status
What works today:
- TLS 1.3 handshake with classical or post-quantum (ML-KEM) key exchange
GET/POST/HEAD/PUT/DELETE, sync and async- HTTP/1.1 response framing (content-length, chunked, gzip/deflate)
- Connection keep-alive with a per-host pool; automatic redirect following
- Chain + hostname certificate verification, certifi default + custom CA trust
Current limitations:
- TLS 1.3 only (a Fizz constraint) — it cannot talk to TLS 1.2-only servers
- HTTP/1.1 only (no HTTP/2)
Building
The post-quantum handshake requires a Fizz built against
liboqs. The CI wheels build the
whole folly + Fizz + liboqs tree from source inside manylinux_2_28; see
BUILDING.md for that recipe and for local development builds.
Metadata
Release files for fizzpy 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fizzpy-0.4.0.tar.gz | 435.8 kB | Details |
Built distributions (wheels)
Total release size: 74.5 MB
Release files / fizzpy-0.4.0.tar.gz
| Download URL | fizzpy-0.4.0.tar.gz |
|---|---|
| Size | 435.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3105bb4f08bbcc96d93dbd12c56397a364d5449b481205097b0a9009860e3b97
|
|
BLAKE2b-256 checksum How to use checksums |
59cff5e0d2e93965977309753ee489e52dd59de625785c30b2889bf39834cae5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp314-cp314-win_amd64.whl
| Download URL | fizzpy-0.4.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 3.3 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b96a73fe17666720d96d59411f91e052fe4d4d77f2bba8ea557bffc53d7657a6
|
|
BLAKE2b-256 checksum How to use checksums |
767cac088a12c30500f74126102581533b9ac1f871cafb443d3d42cb957658bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | fizzpy-0.4.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ed997460d6a1623320a9915157540999079f1a7904cfa6a3ecc38fe987a430de
|
|
BLAKE2b-256 checksum How to use checksums |
291f3cde23c30c5070cfe08296b76bde834e43637058315d0ceddf4eeeafb5f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp314-cp314-macosx_15_0_x86_64.whl
| Download URL | fizzpy-0.4.0-cp314-cp314-macosx_15_0_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.14 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
07827e586eb1a316e268e1f055e5ed4d858893130cf41788afae2fb97b429760
|
|
BLAKE2b-256 checksum How to use checksums |
83559f4e5d80ba1930789ae42b7f7308db778ac2e06d3259d799e305aa05f034
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp314-cp314-macosx_14_0_arm64.whl
| Download URL | fizzpy-0.4.0-cp314-cp314-macosx_14_0_arm64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.14 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3d6d1af8bd0c03f6da0979be49f9084edb67f395e724d47c758747096978b6b0
|
|
BLAKE2b-256 checksum How to use checksums |
c240fcd17d4e40e8fa8944dd98d8363ba1d36939ebacc16956dfde9be01172e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp313-cp313-win_amd64.whl
| Download URL | fizzpy-0.4.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7fc8d175e4e801d88f28da6a155b3e7f822d51590a7761501e5873676da66a1b
|
|
BLAKE2b-256 checksum How to use checksums |
83c676d94ac4919bb9bfded1de463f081023dc3209a1d841833c221e760a5f51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | fizzpy-0.4.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5ff7eeebdeb226c5c2d862994d9434268882d5d9717dd02a3ba8ff66ace45908
|
|
BLAKE2b-256 checksum How to use checksums |
c6abb11675e5c079f56d04e1f5d6643957a7631b128953af8514e36fffa3c88e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp313-cp313-macosx_15_0_x86_64.whl
| Download URL | fizzpy-0.4.0-cp313-cp313-macosx_15_0_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.13 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
6005804d26aa820318b356ecfdac98d5e86eed999eb16d174bf635dd97c12713
|
|
BLAKE2b-256 checksum How to use checksums |
414d0f94d94e5e0651bc01a1d4d111ffd0443d7dfc9b35f95a333a0dbdd20053
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp313-cp313-macosx_14_0_arm64.whl
| Download URL | fizzpy-0.4.0-cp313-cp313-macosx_14_0_arm64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.13 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a9ccbcfc73d399863ed8410e0c023f48a303089d61814e2b32f7de28e22ad89e
|
|
BLAKE2b-256 checksum How to use checksums |
5bbcda49760f7407e657fd73047f73bc3865ea340fdf834c2d8812b754c3c7fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp312-cp312-win_amd64.whl
| Download URL | fizzpy-0.4.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b96daf5687f67da2e728f3492a4327b8495cff0b48fce63eeb62a9887e4488c3
|
|
BLAKE2b-256 checksum How to use checksums |
4af38293351553d96f248413da106b82429ebe2d5d5ff30117b069538455bec2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | fizzpy-0.4.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8e76723a1beea04149dcae81ea8c6469c9d3ebb105f30c6a20ee066c9c8f216
|
|
BLAKE2b-256 checksum How to use checksums |
76454cc8a5e6046e1ba5cdf83a8939782649f0ffb1d78bcf41bfd8ea2a6acc46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp312-cp312-macosx_15_0_x86_64.whl
| Download URL | fizzpy-0.4.0-cp312-cp312-macosx_15_0_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.12 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
84a061088f55e9e89ffc4c634c0af3863a08e0a84c6e42a5ac888ccea258a60c
|
|
BLAKE2b-256 checksum How to use checksums |
e2bc91a7ed914e6ccd6170b0192b9033b3ad398bcac2474987eb0638f3ea69f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp312-cp312-macosx_14_0_arm64.whl
| Download URL | fizzpy-0.4.0-cp312-cp312-macosx_14_0_arm64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.12 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
bb998fbd71313bc9b8a93f1edee4565860e9c9092aa5a2baaf18e879a9dc0c98
|
|
BLAKE2b-256 checksum How to use checksums |
9ed6826ba12e5d4f94dbfee505c9d2f62bcc48694b743f8dfc418e9dc2c1691b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp311-cp311-win_amd64.whl
| Download URL | fizzpy-0.4.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9db9a0a4ced3e173fd77995d83252301ca4809c3aa9bd8e9df6eb47d2bb4a726
|
|
BLAKE2b-256 checksum How to use checksums |
07b9a9220ee54e29146491da11f885ecdac7111a1b257313cf83c10f11500a91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | fizzpy-0.4.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
51bcd3a808456b3a678c4b9abd22a624ca8cab553f8dcb2bd1274b71ba596c65
|
|
BLAKE2b-256 checksum How to use checksums |
1e93e92cc4b873c9d52c710274d75848aa6fccecbac12781304b60aaab83570a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp311-cp311-macosx_15_0_x86_64.whl
| Download URL | fizzpy-0.4.0-cp311-cp311-macosx_15_0_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.11 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
20e2fe5b37adf29f88fbfc1c58cb7e831fb867f17d3e52509b381abc14115a57
|
|
BLAKE2b-256 checksum How to use checksums |
10f85d892d07d2587f031790bfa4c5efabdb8ffe5d06229fab6fc13863c9e0d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp311-cp311-macosx_14_0_arm64.whl
| Download URL | fizzpy-0.4.0-cp311-cp311-macosx_14_0_arm64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.11 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b72888ca0897ef63902c20a015f3c5a6e6b0383f368558f12ef7080daf655e7e
|
|
BLAKE2b-256 checksum How to use checksums |
d6fabe22c00808f09c583eef713d91a0eea327fa716cebceb726c6120c379a22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp310-cp310-win_amd64.whl
| Download URL | fizzpy-0.4.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
30bb1e2ccec02fea657fca3a2e7612e9ef956f9f31b701a646f7a5e3c55ba588
|
|
BLAKE2b-256 checksum How to use checksums |
9747e2285941d39deeeabeb33beeb505557febf4b08df6838fc44009877b2ca1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | fizzpy-0.4.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
43151a29c10613c599f02819e12564668b5c241c85fc45a25f5bad4fe82a62b6
|
|
BLAKE2b-256 checksum How to use checksums |
b4f7a38666930708466bda5cf558d060cd791706a94f71677da38bce5bdcc290
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp310-cp310-macosx_15_0_x86_64.whl
| Download URL | fizzpy-0.4.0-cp310-cp310-macosx_15_0_x86_64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.10 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
229306c8b025c4a3a41a668af081b7f0dbbce585a50182596dc30655ed9fa17a
|
|
BLAKE2b-256 checksum How to use checksums |
f3821a91c7b390b3c0fdc315994c5e1af127cf5931906411dcd72dfa759f7a9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / fizzpy-0.4.0-cp310-cp310-macosx_14_0_arm64.whl
| Download URL | fizzpy-0.4.0-cp310-cp310-macosx_14_0_arm64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.10 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9bf0e9d8ca4dfa646c46fef234ae0570877a373ab19e77061f8f604f48f0be5f
|
|
BLAKE2b-256 checksum How to use checksums |
051b46442c831714800d89e750c8a1ad090cfccb4357c8ec45fdb2f1871a948b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency log