2 Commits

Include renames

Author	SHA1	Message	Date
Chris Tsang	f9112c5ba9	Ship the Python README as the PyPI description ... The `vtracer` package never declared a `readme`, so its PyPI page rendered an empty description. Point `[project].readme` at the crate's README, and mirror it in Cargo.toml alongside the core crate's convention. Pin the documented install to 1.0.0a2 while the 1.0 line is pre-release: `--pre` would resolve it, but a bare `pip install vtracer` still lands on 0.6.15, whose cp314 wheels segfault on any keyword argument (pyo3 0.19 predates CPython 3.14 moving `PyTupleObject::ob_item`, #124).	2026-07-31 16:35:01 +01:00
Chris Tsang	f76aed78b2	Add vtracer-py: Python bindings with a rich API ... New crates/vtracer-py (pyo3 + maturin, abi3) wrapping the vtracer framework. Rather than a thin CLI-style wrapper, it exposes a mutable `Config` class with named properties and `bw`/`poster`/`photo` preset constructors, plus three input paths — `convert_file`, `convert_bytes` (encoded image, optional format), and `convert_pixels` (raw RGBA8) — available as `Config` methods and module-level functions. Palette is a list of `#rrggbb` strings; bad inputs raise ValueError. The core crate stays pure: image decoding lives here. The crate is excluded from the cargo workspace (pyo3 extension-module cdylibs don't link libpython, which breaks `cargo test` at the root) and is built with maturin. Ships a vtracer.pyi type stub. README updated.	2026-07-24 11:53:47 +01:00