Skip to main content

imgread

A public beta Python library for decoding JPEG, PNG and TIFF into NumPy arrays, with a Rust decoder and a statically linked libjpeg-turbo backend.

python -m pip install --pre imgread

Use a wheel on a supported platform; it needs no Rust toolchain. To require a wheel: python -m pip install --pre --only-binary=:all: imgread. A source build requires Rust 1.88 or newer, CMake, a C compiler and NASM.

from pathlib import Path
import imgread

# Path and os.PathLike[str]
rgb = imgread.load_numpy(Path("photo.jpg"))

# bytes, bytearray, memoryview or a uint8 NumPy buffer (including strided views)
bgr = imgread.load_numpy_from_bytes(Path("photo.png").read_bytes(), color="bgr")

# Choose the portable Rust decoder explicitly
rgb = imgread.load_numpy("scan.tiff", backend="image")

Array and format contract

Every successful call returns a new writable, C-contiguous numpy.ndarray of shape (height, width, 3) and dtype uint8. The default order is RGB; color="bgr" reverses the channels. Only dtype="uint8" is supported. Color, dtype, backend and limit-profile names are case-insensitive. Bytes paths are rejected; use the buffer APIs for encoded bytes. Decoding releases the GIL. The standalone buffer functions copy their input; Loader.decode borrows immutable bytes for the duration of the call and copies other buffer types before releasing the GIL.

  • JPEG: baseline, progressive, grayscale and CMYK. CMYK may use the fallback decoder. Decoder rounding and chroma upsampling can produce small pixel differences between backends; bit-for-bit JPEG parity is not promised.
  • PNG: grayscale, RGB, RGBA and 16-bit input. Alpha is discarded without compositing. Grayscale is replicated into three channels. Unsigned 16-bit values are rounded to 8 bits using (value + 128) // 257.
  • TIFF: the first page only, without applying orientation. Common uncompressed, LZW and Deflate variants and little-/big-endian samples are supported. Supported encodings follow the image TIFF decoder; unsupported encodings raise errors.
  • EXIF orientation, ICC color conversion and other metadata are not applied or returned. Pixels remain in the encoded color space. Animated PNG returns its default image, not an animation.

Other formats are rejected even though the underlying Rust image dependency retains its default features in this beta.

Persistent Loader

Requires imgread 0.2.1 or newer. See the changelog for release details.

loader = imgread.Loader(color="rgb", backend="auto")
rgb = loader("photo.jpg")
data = Path("photo.jpg").read_bytes()  # or an encoded image from another source
rgb = loader.decode(data)

indexed = imgread.Loader(["first.jpg", "second.jpg"])
rgb = indexed[0]

decode(data) accepts the same uint8-compatible buffers as load_numpy_from_bytes, including strided views, and uses the Loader's fixed options and resource limits. It reuses the same native JPEG state as path/index calls and returns an independent array. Input buffers are never retained. Mutable buffers and memoryviews, including read-only views, are copied in C order; immutable bytes require no input copy. max_buffer_bytes caps retained file-read storage only, not the accepted image size.

A Loader can be pickled and passed to DataLoader workers: each process initializes its own decoder lazily. Keep one Loader per worker; overlapping or reentrant calls on the same instance raise RuntimeError. Buffer data belongs to the caller and is not included in the Loader's pickle. Preloading an entire dataset is optional and has its own memory and worker-startup costs.

Backends and the simple API

backend="auto" selects TurboJPEG for JPEG when compiled in and image otherwise. backend="image" always selects the Rust decoder. backend="turbojpeg" falls back to image when unavailable, incompatible with the format, or unable to decode it. A successful fallback emits RuntimeWarning. An unsuccessful decode raises an error. auto also warns if an attempted TurboJPEG decode falls back. Inspect the build with imgread.supported_backends(); official wheels include TurboJPEG.

load_numpy_simple(path, *, limits="safe") and load_numpy_simple_from_bytes(data, *, limits="safe") are JPEG-only RGB shortcuts. They use the same checked decoder and warning/fallback behavior. Non-JPEG input is always a ValueError. Python's normal warnings filters control every warning, including always, ignore and error; the library has no global deduplication.

Resource limits

All four decode functions accept the keyword-only argument limits="safe":

Budget per image Default cap
Encoded input 256 MiB
Width / height 32,768 each
Pixels 100,000,000
RGB/BGR output 512 MiB
Decoder allocation budget 512 MiB

Input size is checked before copying a Python buffer or reading a regular file. The open file is read with a bound even if it grows. Dimensions and output sizes are checked before the pixel allocation. A resource-limit failure is terminal: no fallback can retry it with another decoder.

The decoder budget is passed to image::Limits and to libjpeg-turbo's intermediate buffer memory limit. The image JPEG backend also preflights a conservative working-set bound covering padded coefficient planes, decoded pixels and row/upsampling buffers, because its upstream JPEG decoder ignores max_alloc. This applies to fallback routes too, and may reject a large JPEG even when its final pixels fit the output cap (including baseline JPEGs that need less memory). These budgets do not measure total process RSS: encoded input, output, metadata, conversion buffers, allocator overhead and concurrent calls can add to it. It is a per-image policy, not a process sandbox.

For trusted large inputs only, use limits="unlimited". This removes policy caps; checked arithmetic, address-space checks and fallible application allocations remain enabled. It makes no speed promise. Ordinary allocation pressure and upstream codec behavior can still cause errors.

Errors

Condition Exception
Invalid input type, including bytes paths TypeError
Invalid option, unsupported format or resource limit ValueError
Missing file FileNotFoundError
Permission denied PermissionError
Directory used as input IsADirectoryError
Other filesystem failure OSError subclass with OS errno
Corrupt or undecodable image RuntimeError
Successful backend fallback RuntimeWarning

Format detection uses content; for path input an extension is a last resort for identifying a damaged image. Unknown bytes raise ValueError; a recognized but corrupt image raises RuntimeError.

Beta support and stability

The release wheel matrix targets CPython 3.11–3.14, Linux x86_64 manylinux2014 (glibc 2.17+) and macOS x86_64 (10.13+) / arm64 (11.0+). Windows, Linux aarch64, musllinux, PyPy, free-threaded CPython and Python 3.15 are not supported by this beta. The 3.15 compatibility CI job is informational.

Loader and the five functions above form the beta API. Bug fixes can change rejection of malformed inputs, limits or decoder results. Intentional API changes will be recorded in release notes and beta versions; pin a version for reproducible work. The Rust crate is internal and is not published to crates.io.

Development

Use uv run for Python-facing commands. Normal builds and tests use the committed Cargo.lock and uv.lock without updating them.

uv sync --locked --no-install-project
uv run maturin develop --locked
uv run pytest python_tests -q
cargo test --locked
cargo test --locked --features turbojpeg
cargo fmt -- --check
cargo clippy --locked --all-targets --all-features -- -D warnings
uv run maturin build --release --locked --sdist
uv run twine check target/wheels/*

Keep maturin's configured features when building; passing --features extension-module alone overrides them and removes TurboJPEG.

Publishing

Releases are built and published by GitHub Actions. Run Build distributions (beta-build.yml) on a release branch to validate the full package matrix without publishing.

  1. Update Cargo.toml, its root Cargo.lock entry and CHANGELOG.md, then merge the reviewed changes into main.
  2. Permit the release tag in the GitHub pypi environment deployment policy. Currently only v0.2.1 is allowed. Keep its required reviewer enabled.
  3. Create and push an annotated tag matching the package version, for example git tag -a v0.2.1 -m 'Release imgread 0.2.1' followed by git push origin v0.2.1. These commands assume that tag does not exist yet.
  4. Publish release checks the tag/version and runs CI. It builds and tests 12 wheels (CPython 3.11–3.14; Linux x86_64 and macOS x86_64/arm64), rebuilds the sdist, validates package metadata and saves SHA256SUMS.
  5. Review the successful build and approve the pypi deployment in Actions. The job publishes the same artifacts using PyPI Trusted Publishing.
  6. The workflow installs the published wheels on all 12 combinations, verifies PyPI file hashes, and publishes GitHub release notes with those artifacts.

Configure the PyPI project's GitHub Trusted Publisher with owner ayasyrev, repository imgread, workflow release.yml, and environment pypi. GitHub also requires the Actions variable PUBLIC_RELEASE_REPOSITORY=ayasyrev/imgread. See PyPI's setup guide.

uv build produces a local verification build. On Linux it may generate a linux_x86_64 wheel, which PyPI rejects. The workflow builds portable manylinux2014 wheels in the matching container. Do not rename a local wheel or publish the local dist/ directory as a release.

For interrupted releases, retain the original tag and Actions artifact set. Inspect any existing PyPI files before retrying an upload; a rebuild is not a replacement for already published files. Rerun only failed jobs when possible. If only the GitHub release job failed, rerun that job: it can finish an existing draft after verifying its input against PyPI, and refuses to overwrite a public GitHub release.

License

The project uses the MIT license. Redistributed dependency notices are in THIRD_PARTY_NOTICES.md and licenses/ and are included in both wheels and sdists.

This software is based in part on the work of the Independent JPEG Group.

Loader: paths and saved indices

Loader(
    paths=None, *, color="rgb", dtype="uint8", backend="auto",
    limits="safe", max_buffer_bytes=1048576,
)

The signature above describes the keyword-only options. For a working call:

loader = imgread.Loader(color="bgr")
array = loader("photo.jpg")

indexed = imgread.Loader(["first.jpg", "second.png", "first.jpg"])
first = indexed[0]
last = indexed[-1]
other = indexed("outside-the-snapshot.tiff")

paths is a finite iterable of str or os.PathLike[str]; a single path or bytes container is rejected. Construction converts each element once and preserves its text, order and duplicates in an immutable native snapshot. It opens no images, checks no image metadata and creates no native decoder. Changing the original list or PathLike objects does not change this snapshot. Files remain mutable: each call opens the current file, and relative paths use the working directory at load time.

len(indexed) counts snapshot entries. An empty snapshot is valid. Without a snapshot, length and indexing raise TypeError; path calls still work. bool(loader) is always true. Indexing accepts the integer __index__ protocol, including NumPy integers and negative indices. Out-of-range integers, even huge ones, raise IndexError. Python bool, slices and collections of indices raise TypeError. Settings cannot be changed after construction.

Loader returns the same pixels, exceptions and fallback warnings as load_numpy with the same build, backend and settings. Each array owns separate writable memory and remains valid after later calls, failures or Loader deletion. No output cache, batch API or internal prefetch is added.

max_buffer_bytes limits the capacity of compressed input retained after a call; its default is 1 MiB, and zero disables input retention. It accepts non-negative addressable integers through __index__. Larger allowed files use temporary input storage. This cap is separate from limits, native decoder allocations, the path snapshot and returned arrays; it is not a total RSS limit. Native JPEG state may still be reused with a zero input cap. A conservative JPEG marker check prevents a previous image's tables from affecting a later decode. Uncertain files use fresh native state and the usual fallback rules.

One Loader allows one active image call. Overlap and reentry raise RuntimeError("Loader is busy") immediately, including reentry from path/index protocols and warning handlers. Different instances operate independently. I/O and decoding release the GIL. Pickle stores only configuration and snapshot strings; restored objects start with no input/native state. Spawn, forkserver and an idle fork create process-owned decoding state. Fork while a Loader call is active is unsupported. Long-lived workers retain at most one workspace per Loader; process startup, manifest copies and pickle costs remain part of application preparation.

For PyTorch, ImageFolder(..., loader=Loader()) calls Loader with a path. Use a transform that accepts NumPy arrays and restrict the dataset to supported image formats. An indexed Dataset can snapshot paths in a Loader and call loader[index], keeping labels alongside the paths. Torch and torchvision are optional integrations, never imgread runtime dependencies.

Metadata

Release files for imgread 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for imgread 0.2.1
File Size Uploaded
imgread-0.2.1.tar.gz 139.3 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for imgread 0.2.1
File
imgread-0.2.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details
imgread-0.2.1-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details
imgread-0.2.1-cp314-cp314-macosx_10_13_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.13+ x86-64 Details
imgread-0.2.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details
imgread-0.2.1-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details
imgread-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details
imgread-0.2.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details
imgread-0.2.1-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
imgread-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details
imgread-0.2.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details
imgread-0.2.1-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details
imgread-0.2.1-cp311-cp311-macosx_10_13_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.13+ x86-64 Details

Total release size: 15.0 MB

Release files / imgread-0.2.1.tar.gz

Download URL imgread-0.2.1.tar.gz
Size 139.3 kB
Tags Source
SHA-256 checksum
How to use checksums
511dff2bc1bb4ca4cec9b632322d45fad4c2fd70118dc8771b8c5840e6e8ce94
BLAKE2b-256 checksum
How to use checksums
f3859e31eb8f48cb2120fa1188ce2e5e4486a660de164480b744a49aae0c1c1f
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL imgread-0.2.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 1.3 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
1cf843723fb40a42be48eff25d6a317b95af2216f5866091801344ba75f2558a
BLAKE2b-256 checksum
How to use checksums
47245645765e1bd7cc7c4e77f043811090ff0e9711a206475a16fd0c3e8c7900
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp314-cp314-macosx_11_0_arm64.whl

Download URL imgread-0.2.1-cp314-cp314-macosx_11_0_arm64.whl
Size 1.2 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f40972c0541e20c48cc97e5daae2f40268cde390cb02b8e3b8c02db9b97182d7
BLAKE2b-256 checksum
How to use checksums
b469331a5d1deb02144685cddd2b4274ebcbb8d60b29d3078a3a5feb7bcea71f
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp314-cp314-macosx_10_13_x86_64.whl

Download URL imgread-0.2.1-cp314-cp314-macosx_10_13_x86_64.whl
Size 1.2 MB
Tags CPython 3.14 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
1171822954638fad2da27ee6c1a7c7f5dd42ae4c949a057ad264da24fec3e80f
BLAKE2b-256 checksum
How to use checksums
169f3054cc8a8eca53059c62ee4fce9968f151aac2bd6fb567881dec01c0d332
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL imgread-0.2.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 1.3 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
662e6d163bb045ea9c8f67671847005dc804e614e46496aa05b6acdef582fc5e
BLAKE2b-256 checksum
How to use checksums
3f6bdeb7ad8cd3c3c82f5e047f60271b8aa1db6b76dadb49e1844d741a34db48
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp313-cp313-macosx_11_0_arm64.whl

Download URL imgread-0.2.1-cp313-cp313-macosx_11_0_arm64.whl
Size 1.2 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
cdae5c364db5371944a8b2a1cd762ede4c8ad867e25f1b5cd1b150fa3cf582e9
BLAKE2b-256 checksum
How to use checksums
5995ea452497bbeecbacc90a3f21a35c8d6cf9444f370eb5e6dd67756721bed7
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl

Download URL imgread-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl
Size 1.2 MB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
cfab04de20cbcbd02c5da95f6f07f1527d5b5300884178eee7de11662f9ce751
BLAKE2b-256 checksum
How to use checksums
e1e8abaca91e3a3530c258d79cc8f3e5d54007c13bf75914d2c5783c0a15fcd3
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL imgread-0.2.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 1.3 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
201ac78575c300f7e22fe0c2230796c0b38cd02813e6b4cfbf01ed84b0fd2bb9
BLAKE2b-256 checksum
How to use checksums
b99b8e01b1d0222660022ae49225e5be16b282c110db2ea7202edfc99390ff05
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp312-cp312-macosx_11_0_arm64.whl

Download URL imgread-0.2.1-cp312-cp312-macosx_11_0_arm64.whl
Size 1.2 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
56e27a1b121fb5589f492cc6da1ea4ba91220bebf273ac1da29a9077ffe683cb
BLAKE2b-256 checksum
How to use checksums
685815ea8bea29bc034b93f11232c38d9ecce96b2fe3b335ae0e5e60940be18b
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl

Download URL imgread-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl
Size 1.2 MB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
2a61959a44bb9e85253866f0042be4f9345294f004c5b440b49f9b567f793cd1
BLAKE2b-256 checksum
How to use checksums
26d6b359ce2a2c40124785b890fa56a3fc36fde301b39365e79d07f6030901df
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL imgread-0.2.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 1.3 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
4c12a5fe6277c9e18b4e1d022b8d2ca66b2d42437f197b89b16f760be04d0097
BLAKE2b-256 checksum
How to use checksums
edaaaef24814e74b988eea0b251ba4848296b90ceb272f0b409bc2cffe4993bd
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp311-cp311-macosx_11_0_arm64.whl

Download URL imgread-0.2.1-cp311-cp311-macosx_11_0_arm64.whl
Size 1.2 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
1adb68aa45e7fbdd57d481d66f292c74317a35dcae619fa1277d6c8f664b36ae
BLAKE2b-256 checksum
How to use checksums
c502aec8319cdb31f6331f218e5beb48a32e7155e97c28ecde2a0b4be48eb73c
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 Sep 16, 2026.

Transparency log

Release files / imgread-0.2.1-cp311-cp311-macosx_10_13_x86_64.whl

Download URL imgread-0.2.1-cp311-cp311-macosx_10_13_x86_64.whl
Size 1.2 MB
Tags CPython 3.11 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
86984d004200506d7bff65464599159f0418f2251121eed7be2d47de9138c7b6
BLAKE2b-256 checksum
How to use checksums
e6f20ead7a284dc75dfe21cadec08a8e9d49086a0d48f1f276320c22da47b885
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 Sep 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.0

13 release files

This release

0.2.1 This release

13 release files

0.0.1

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page