ouestcharlie-imageproc
Image processing coprocessor for OuEstCharlie — a Rust CLI (image-proc) bundled with a Python subprocess wrapper.
Handles all pixel-level operations: decoding, EXIF orientation, resize, fit, and encoding to AVIF or JPEG. Used by ouestcharlie-py-toolkit for thumbnail grid assembly and on-demand preview generation.
What's in this package
image-proc— Rust CLI that reads JSON requests from stdin and writes JSON responses to stdout (newline-delimited, persistent coprocessor model).ouestcharlie_imageproc.image_proc— Python subprocess wrappers:OneTimeImageProc(fresh process per request) andPersistentImageProc(long-lived process with asyncio lock).
Supported formats
| Format | Notes |
|---|---|
| JPEG, PNG, WebP, TIFF | Default, pure Rust, all platforms |
| RAW (CR2, NEF, ARW, DNG, RAF, ORF, RW2, PEF) | Enable with IMAGE_PROC_FEATURE_RAW=1 |
| HEIC/HEIF | Enable with IMAGE_PROC_FEATURE_HEIC=1 — bundled into published wheels by default; requires libheif at build time only, none at runtime (its shared library is vendored into the wheel) |
Building
Requires Rust stable, nasm, and (for HEIC) libheif:
# macOS
brew install nasm inih libheif
# Linux
sudo apt-get install nasm libheif-dev
# Windows
choco install nasm
# libheif via vcpkg — see .github/workflows/_build.yml for the bootstrap steps
# Install as editable (development)
pip install -e . --no-build-isolation
# Build release wheel
IMAGE_PROC_FEATURE_RAW=1 IMAGE_PROC_FEATURE_HEIC=1 hatch build --target wheel
Published wheels set both IMAGE_PROC_FEATURE_RAW and IMAGE_PROC_FEATURE_HEIC via
CI — a bare pip install -e . or hatch build without the env vars excludes both,
same as cargo build without --features.
Running tests
# Unit tests (no binary required)
.venv/bin/python -m pytest tests/ -v
# Integration tests (require compiled binary)
.venv/bin/python -m pytest tests_integration/ -v
# Rust tests
cd image-proc && cargo test
Design
See imageproc_LLD.md for the protocol specification, command reference, and build details.
Release files for ouestcharlie-imageproc 2.3.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 | |
|---|---|---|---|
| ouestcharlie_imageproc-2.3.0.tar.gz | 2.7 MB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ouestcharlie_imageproc-2.3.0-cp313-cp313-win_amd64.whl | CPython 3.13 | CPython 3.13 | Windows x86-64 | Details |
| ouestcharlie_imageproc-2.3.0-cp313-cp313-manylinux_2_34_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.34+ x86-64 | Details |
| ouestcharlie_imageproc-2.3.0-cp313-cp313-macosx_26_0_arm64.whl | CPython 3.13 | CPython 3.13 | macOS 26.0+ ARM64 | Details |
Total release size: 21.1 MB
Release files / ouestcharlie_imageproc-2.3.0.tar.gz
| Download URL | ouestcharlie_imageproc-2.3.0.tar.gz |
|---|---|
| Size | 2.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4be768a456b461a7261f8f65cefdeb1b2ff46602cf9b0375a00206462361962
|
|
BLAKE2b-256 checksum How to use checksums |
00cb7426e353fa7217ac7897bcc4867676b18f3da36f8c9a0831e27732f19098
|
| 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 7, 2026.
Transparency logRelease files / ouestcharlie_imageproc-2.3.0-cp313-cp313-win_amd64.whl
| Download URL | ouestcharlie_imageproc-2.3.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c9d7793a548443fae6d507a34d56a2f83f12ada08b015a21d2aeeb8dc0f48ca0
|
|
BLAKE2b-256 checksum How to use checksums |
ac07f5b37c480cd79ff00d6841e3de2d047b30bfb22e700bfcf14b471f7eed5d
|
| 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 7, 2026.
Transparency logRelease files / ouestcharlie_imageproc-2.3.0-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | ouestcharlie_imageproc-2.3.0-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 7.3 MB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
eabf217516e4b889e4baa3642a6f0c60dccfbbae47b2d65d2c34bf714df0da3c
|
|
BLAKE2b-256 checksum How to use checksums |
4503b7e6889f199cae7b787f95f9223eccc40497963417d90a961119db31f5af
|
| 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 7, 2026.
Transparency logRelease files / ouestcharlie_imageproc-2.3.0-cp313-cp313-macosx_26_0_arm64.whl
| Download URL | ouestcharlie_imageproc-2.3.0-cp313-cp313-macosx_26_0_arm64.whl |
|---|---|
| Size | 6.4 MB |
| Tags | CPython 3.13 macOS 26.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4abf2c27ef5022ed1937b29f0ff40db00a9709fb52239606a9ba24313dd613ce
|
|
BLAKE2b-256 checksum How to use checksums |
73ce40aad73d10bef40bec3a6a5dd17f6897054d20913907c7e1344a8a802053
|
| 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 7, 2026.
Transparency log