blitz-py
Render HTML/CSS to images from Python — no browser, no GPU, no JavaScript, no network.
Powered by Blitz, DioxusLabs' modular web engine: real CSS via Stylo (Servo/Firefox's style engine), flexbox/grid layout via Taffy, text shaping via Parley, and CPU rasterization via vello_cpu.
A 240×240 widget renders in ~1.5ms warm on an M-series Mac (~40ms for the first render). Output is deterministic and identical across platforms: the Inter font (SIL OFL 1.1) is bundled as the default face, so text renders the same on your laptop and in a fontless Alpine container.
What it looks like
Unedited output: a Tailwind v4 dashboard (render_png — grid, SVG donut + sparkline, gradients), a 240×240 smart display (one render_layers call over four Template cells, ellipsized title, glow accent), and Bootstrap 5.3 components.
Install
pip install blitz-py
Prebuilt wheels (abi3, Python ≥ 3.10; CI-tested on 3.10–3.15): Linux glibc + musl (x86_64, aarch64, armv7), macOS (arm64, x86_64), Windows (x64, arm64).
32-bit ARM (armv7) wheels are available as of 0.6.0 (e.g. Raspberry Pi OS 32-bit); CI runs the full test suite on them under QEMU. (Home Assistant itself dropped 32-bit support in 2025.12.)
Usage
import blitz_py
png = blitz_py.render_png(
"""
<style>
body { margin: 0; background: #000; color: #fff; font-family: sans-serif; }
.screen { display: flex; flex-direction: column; align-items: center;
justify-content: center; height: 240px; }
.temp { font-size: 64px; font-weight: 600; }
.label { color: #8e8e93; }
</style>
<body><div class="screen">
<div class="temp">21.5°</div>
<div class="label">Living room</div>
</div></body>
""",
width=240,
height=240,
)
with open("out.png", "wb") as f:
f.write(png)
Or get raw pixels for Pillow:
from PIL import Image
w, h, rgba = blitz_py.render_rgba(html, width=240, height=240)
Image.frombytes("RGBA", (w, h), rgba).convert("RGB").save("out.jpg", quality=90)
Animated GIFs
Everything above is Tailwind classes + CSS @keyframes (source): satellites on different orbital periods, a live-scrolling traffic chart (a periodic series drawn two cycles wide, translated one cycle per loop — new data appears to stream in), an indeterminate progress sweep, and a steps()-driven typewriter — 48 frames rendered in ~220ms, seamless 4s loop.
CSS animations are evaluated on a deterministic clock: render_frames renders the document at any list of timestamps (seconds), and Pillow assembles the GIF. Frames after the first reuse the parsed document, so they're fast — ~1ms per 240×240 frame:
fps, seconds = 12, 3.2
gif = blitz_py.render_gif(
html, width=240, height=240,
times=[i / fps for i in range(int(fps * seconds))],
)
open("widget.gif", "wb").write(gif) # ~16KB, encoded natively in ~20ms
Anything @keyframes can express — transforms, opacity, colors — loops perfectly because you control the clock. The encoder uses one shared palette (colors=64 by default), no dithering, and transparency-based inter-frame deltas — the combination that keeps UI-animation GIFs small. Frame delays follow the spacing of times. See examples/animated_widget.py.
Need custom encoding (dithering, APNG/WebP, per-frame palettes)? render_frames returns raw RGBA frames for Pillow/ffmpeg.
Fast repeated renders: Template
For dashboards and device widgets that re-render the same document with fresh data, parse once and mutate by element id:
tpl = blitz_py.Template(html, width=240, height=240)
tpl.update(temp="21.5°", hum="48%") # batch text update, one round-trip, atomic
tpl.set_html("alerts", "".join(f"<li>{a}</li>" for a in alerts)) # re-render a region
tpl.set_style("bar", "width", "62%")
tpl.set_attribute("icon", "src", data_uri)
jpeg = tpl.render_jpeg(quality=90) # ~0.5ms — straight to the device
gif = tpl.render_gif(times=[i/12 for i in range(38)]) # animated, current data
Templates are safe to share across threads (the document lives on its own worker thread), and renders release the GIL — 4 rendering threads get ~3.5× throughput.
Recipes
OG / social cards — deterministic, ~6ms per 1200×630 card, no Chromium to babysit:
card = blitz_py.render_png(OG_TEMPLATE, width=1200, height=630,
css_vars={"title": post.title, "kicker": post.tag})
Email-HTML previews — auto-height gives you the full message at client width:
png = blitz_py.render_png(email_html, width=600) # height=None → sized to content
Visual snapshot tests — renders are byte-identical across platforms (CI-verified), so hashes are stable for a given blitz-py version (engine upgrades can shift pixels; re-record on upgrade):
def test_widget_looks_right():
png = blitz_py.render_png(widget_html, width=240, height=240)
assert hashlib.sha256(png).hexdigest() == "9d62e494..." # exact, on every OS
Device dashboards (the original use case) — Template + render_jpeg/render_gif for sub-millisecond updates pushed to small displays.
API
Six functions and a class, same keyword arguments:
render_png(html, *, width, height=None, ...) -> bytes # PNG; height=None → content height
render_jpeg(html, *, width, height=None, quality=90, ...) -> bytes # JPEG (opaque background)
render_rgba(html, *, width, height=None, ...) -> (w, h, bytes) # raw RGBA pixels
render_frames(html, *, width, height, times, ...) -> (w, h, [bytes, ...]) # animation frames
render_gif(html, *, width, height, times, colors=64, ...) -> bytes # looping GIF, native encoder
Template(html, *, width, height, ...) # parse once, re-render fast
Template methods: set_text(id, text) · update(**id_to_text) (batch, atomic) · set_html(id, fragment) (replace a region, new ids indexed) · set_style(id, prop, value) · set_attribute(id, name, value) · render_png/jpeg/rgba(time=...) · render_frames(times=...) · render_gif(times=..., colors=...)
Layered compositing
render_layers composites several documents and/or Templates into one surface in a single call — positions, paint order, alpha, and clipping handled in Rust, with native PNG/JPEG output. Per-layer blur and tint unlock effects the engine can't do in CSS, like text glow:
frame = blitz_py.render_layers_jpeg(
[
{"html": backdrop_html, "width": 240, "height": 240},
{"template": clock_cell, "x": 8, "y": 8}, # Templates re-render in ~0.4ms
{"template": temp_cell, "x": 124, "y": 8},
{"html": glow_html, "width": 240, "height": 240, "blur": 8, "tint": "#00d9ff"},
{"html": glow_html, "width": 240, "height": 240}, # sharp pass on top
],
width=240, height=240, background="#000000", quality=90,
)
Layers paint in list order (explicit z-order) and are clipped to their rects — a whole multi-widget display becomes one call.
Layout introspection
Ask the engine where things actually landed instead of mirroring CSS math in Python:
tpl.get_box("forecast") # -> (x, y, width, height) in CSS px, post-layout
tpl.boxes() # -> {id: rect} for every element with an id
Text utilities
Ellipsis, clamping, fitting and balancing — computed with the renderer's own shaper so they're exact:
blitz_py.ellipsize(title, max_width=120, font_size=14) # "Living room te…"
blitz_py.line_clamp(desc, max_width=200, max_lines=2, font_size=13)
blitz_py.fit_font_size("23.5°C", max_width=180, max_size=72) # hero autoscaling
blitz_py.wrap_balanced(headline, max_width=200, font_size=18) # text-wrap: balance
blitz_py.measure_text_lines(text, font_size=13, max_width=200) # per-line metrics
blitz_py.register_fonts([font_bytes]) # once, process-wide
Text measurement
measure_text exposes the engine's own shaper (Parley + the same font collection used for rendering), so Python-side fitting logic — ellipsis, autoscaling, wrapping estimates — uses the same metrics the renderer will use, instead of a second font system that drifts:
w, h = blitz_py.measure_text("Living room temperature", font_size=16, font_weight=600)
_, wrapped_h = blitz_py.measure_text(long_text, font_size=14, max_width=208.0)
def ellipsize(text, max_w, **kw):
while text and blitz_py.measure_text(text + "…", **kw)[0] > max_w:
text = text[:-1]
return text + "…"
| Argument | Default | Meaning |
|---|---|---|
width, height |
required | CSS-pixel viewport size |
scale |
1.0 |
Device-pixel ratio; output is width*scale × height*scale physical pixels. Use 2.0 for supersampled/hi-dpi output. |
color_scheme |
"light" |
"light" or "dark" — drives @media (prefers-color-scheme: ...) |
background |
"#ffffff" |
Base canvas color (#rgb, #rrggbb, #rrggbbaa), or None for transparent |
base_url |
None |
Base for resolving relative URLs (must be hierarchical, e.g. file:///assets/) |
css |
None |
Extra CSS appended after the document's styles (wins the cascade) |
css_vars |
None |
Dict of CSS custom properties set on :root, e.g. {"accent": "#f00"} → var(--accent) |
fonts |
None |
List of font file bytes (TTF/OTF, variable fonts OK) to register |
default_font_family |
None |
Family name to use for all CSS generic families (sans-serif, serif, ...) and as text fallback |
allow_file_urls |
False |
Permit file:// URLs for images/resources |
resources |
None |
Dict of URL → bytes served in-memory to <img>, <link rel=stylesheet>, CSS url() and @font-face |
Images and resources
Rendering is fully offline: http(s) URLs are intentionally ignored. Supply assets in memory with resources= — no base64, no filesystem access:
png = blitz_py.render_png(
'<link rel="stylesheet" href="site.css"><img src="icons/logo.png">',
width=400, height=200,
resources={
"site.css": css_bytes, # its url(...) refs resolve relative to it
"icons/logo.png": logo_bytes,
"fonts/brand.woff2": font_bytes, # for @font-face src: url(fonts/brand.woff2)
},
)
Keys resolve against base_url exactly like src/href do, so "logo.png" answers src="logo.png", "./logo.png" and "/logo.png". Templates and html layers accept resources too. Alternatively, embed data: URIs, or set allow_file_urls=True and use file:// paths (reads are capped at 64MB).
Images whose header declares more than 64M pixels are skipped (rendered as missing) rather than decoded — a few-KB "decompression bomb" PNG can otherwise allocate gigabytes.
CSS frameworks (Bootstrap, Tailwind, ...)
Any framework that ships as plain CSS works — inline it in a <style> tag:
css = open("bootstrap.min.css").read() # fetch/cache it however you like
html = f"<style>{css}</style><body class='p-4'><div class='card'>...</div></body>"
Bootstrap 5 components (cards, buttons, badges, alerts, progress bars) render correctly. For Tailwind, run its build step and inline the generated CSS — the JS "Play CDN" won't work because there is no JavaScript engine. JS-driven behavior (modals opening, dropdowns) doesn't apply to static rendering anyway.
Fonts
Bundled Inter is the default for every CSS generic family and the Latin-script fallback, everywhere. Explicit family names (font-family: "Comic Sans MS") resolve against system fonts where available (macOS/Windows natively; Linux via fontconfig loaded at runtime if present — never a link dependency). To use your own font:
font = open("MyFont.ttf", "rb").read()
blitz_py.render_png(html, width=240, height=240,
fonts=[font], default_font_family="My Font")
@font-face also works with resources= URLs (e.g. src: url(fonts/brand.woff2), where the file extension identifies the format), data: and file:// sources. For data: URIs, stating the format is the safe choice, either as the unquoted CSS keyword or a bare extension string (format-less TTF data URIs also load since 0.6.0):
@font-face {
font-family: MyWebFont;
src: url(data:font/ttf;base64,...) format(truetype); /* or format("ttf") */
}
WOFF/WOFF2 sources are supported too (since 0.6.0; earlier wheels silently fell back to the default font). local(...) sources are currently skipped by the engine, and SVG <text> does not see document fonts (see docs/UPSTREAM.md).
Note on coverage: bundled Inter covers Latin scripts (plus Greek/Cyrillic). For CJK, Arabic, and other scripts on systems without suitable fonts, pass an appropriate font (e.g. a Noto variant) via fonts=.
What's supported
Modern CSS as implemented by Stylo/Taffy: flexbox, grid, gradients, border-radius, shadows, transforms, calc(), custom properties, media queries, SVG images, WOFF... No JavaScript and no network: resources come from resources=, data: URIs or opt-in file:// URLs. CSS floats are not laid out (float boxes render as ordinary blocks; the engine's float layout is still opt-in upstream) — use flexbox or grid. Blitz itself is pre-1.0: capable but not pixel-perfect against browsers.
Limits
Guards against inputs that would exhaust memory; all raise ValueError up front unless noted:
- Output: at most 16,384 physical pixels per side and 64M pixels total (256MB of RGBA).
- Animations (
render_frames/render_gif, module andTemplate): at most 1,000 frames, and at most 256M physical pixels summed over all frames of one call (~1GB of RGBA) — e.g. 120 frames at 1920×1080. Split longer animations across calls. - Images whose header declares more than 64M pixels are skipped (rendered as missing), and
file://reads stop at 64MB.
Performance
Measured on an M-series Mac (arm64), each scenario in a fresh process, release build — reproduce with examples/bench.py:
| Scenario | Output px | First render | Warm render | Peak RSS after 200 renders |
|---|---|---|---|---|
<h1>Hello</h1> |
200×100 | 35ms | 0.5ms | 42MB |
| 240×240 widget @2× (flex + gradients) | 480×480 | 32ms | 1.8ms | 45MB |
| Bootstrap 5.3 card (233KB CSS) | 880×720 | 39ms | 8.2ms | 51MB |
| Tailwind v4 dashboard (the gallery image) | 1520×1328 | 60ms | 22ms | 62MB |
| Long article | 800×4000 | 56ms | 21ms | 73MB |
| Animated GIF: widget, 38 frames | 240×240×38 | 56ms total | 1.5ms/frame | 76MB |
GIF encoding on top of rendering (Pillow quantize + LZW, 38 frames): ~60ms, 18KB output.
More performance properties, all verified in CI or by examples/bench.py:
Templatere-renders in ~0.4ms (parse and first style pass amortized away).- Thread scaling: the GIL is released during rendering; 4 threads → ~3.5× throughput.
- Deterministic across platforms: CI renders a golden set on Linux, macOS, and Windows and asserts the outputs are byte-identical. Snapshot tests in your project can compare exact hashes.
- Package ships type stubs (
py.typed), so the API autocompletes and type-checks.
The first render pays a one-time system-font scan; after that the font collection is cached and cloned per render. Importing the module adds ~1MB RSS; memory stays flat under sustained rendering (no per-render growth — verified over 1000+ renders). On an Alpine/arm64 container the warm widget render measures ~0.8ms.
The GIL is released during rendering, so concurrent renders from Python threads scale and async event loops aren't blocked.
Why not a headless browser?
Playwright/Chromium render HTML too — at ~150MB+ of install, a browser process to babysit, and cold starts in the hundreds of milliseconds. blitz-py is a ~7MB self-contained wheel with millisecond renders, suitable for embedded targets like Home Assistant integrations generating widget images for small displays (its original use case).
License
MIT OR Apache-2.0. Bundled Inter font: SIL OFL 1.1 (assets/LICENSE-Inter.txt).
Metadata
Release files for blitz-py 0.6.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 | Provenance | Actions |
|---|---|---|---|---|
| blitz_py-0.6.0.tar.gz | 1.3 MB | With provenance | Details for blitz_py-0.6.0.tar.gz |
Built distributions (wheels)
Total release size: 57.6 MB
Release files / blitz_py-0.6.0.tar.gz
| Download URL | blitz_py-0.6.0.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e9e868bec45ccc2d6abb683151fb1434d9245231d9e8a2dcbcdf8c40609b761
|
|
BLAKE2b-256 checksum How to use checksums |
b52280a789831998b2957bc1a6ccbaa71f48e7574ca3df57337daac71fb43239
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-win_arm64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-win_arm64.whl |
|---|---|
| Size | 4.9 MB |
| Tags | CPython 3.10 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
f3bb7049eab24eb3d40b75b5c819a748ba26944983fffdaf85eac336e5901721
|
|
BLAKE2b-256 checksum How to use checksums |
543a7987de324c68fd621d324ecf4bbb40d322bc8caa057eaae328c18c280fd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-win_amd64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
b04227277a1c83a616a9663b98f5c9626b15309722e9f2943758376e56ca5dd3
|
|
BLAKE2b-256 checksum How to use checksums |
66a8f82a73fa464f669ddc5991733c9415366b1d6acc1299ca3e9bd6e83bea6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
fba07cd689bbed9392462064dbce4e98cb47d2026c1f71bf53df88d3cfd7d491
|
|
BLAKE2b-256 checksum How to use checksums |
83dcd13c44e03a39ef422919b06c8478b7c007d6c3287533ce11e02a5a339305
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-musllinux_1_2_armv7l.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-musllinux_1_2_armv7l.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARMv7l abi3 |
|
SHA-256 checksum How to use checksums |
0af1a75f9d7edd1f27dc78edc1002e4796c6c30f747cf09806d847a25c046c90
|
|
BLAKE2b-256 checksum How to use checksums |
1101371529c8eb0eb30eddeb051a00a842b1ce92e9b8fa1e356736129792fe79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 5.8 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
41c18c8bd793428dbf9be8cc66123038ada636875a8c3c43967a8392c25b5ed9
|
|
BLAKE2b-256 checksum How to use checksums |
1775775789b2925ed11b93c46ec7dcbb944d92e4e6cc8a8f997e319ab8784b07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.9 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
a109c6f974e27477e6c13f427766047578a9b61245271b6076b97ff483dcb8ef
|
|
BLAKE2b-256 checksum How to use checksums |
3093d6ff383f813600c930e4c48db5aea0a5a5175e51102a80909aca356e228e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
e29a7dad9131a2b523ec0f056e784ee06435fc44af24b9e7d5f0620cc8ea65e1
|
|
BLAKE2b-256 checksum How to use checksums |
3b50e413791c5c4e856d2285fee32613b5cfc8634850de901b3e29ec71828615
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 5.8 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARMv7l abi3 |
|
SHA-256 checksum How to use checksums |
c960f7afb6f8496a9ba2ee464b0eecdd4558189c52ffbff0362958aaca4a9956
|
|
BLAKE2b-256 checksum How to use checksums |
4f8dee2d8d590db9aaed68dab4ca3a2efdd9df413b16829d5db5930572eded14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
435533968b578ea97b23af2dbc12ae6139af728342e61bbb6736bd255054e978
|
|
BLAKE2b-256 checksum How to use checksums |
e328822989110f1b059cbdbe14c9d503e3a9034cc91c479ff8a1879335c1774b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / blitz_py-0.6.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | blitz_py-0.6.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
6b821d5f2071c3102679de7d140ff67cd7f974a1f2c31cb9a226aaba3d721605
|
|
BLAKE2b-256 checksum How to use checksums |
e3c3b9ec9560feec87a38502f8ad2745247eef0449864d66c72875b5eba680f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logSecurity for blitz-py 0.6.0
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.
Full provenance
All 11 files in this release have been uploaded with provenance metadata.
Attestation for blitz_py-0.6.0.tar.gz
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 Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.