Skip to main content

rehuco-core

PyPI License: MIT Python versions

Shared library for rehuco: data models, .rehu file I/O, legacy .tc conversion, checksums, a catalog cache, and a task queue.

View on PyPI · View on GitHub

Status

Early. It does real work: it is what the desktop editor reads and writes files with. But it is developed for that one consumer, the .rehu format is still moving, and the API changes without notice. See GitHub Issues for what's in progress.

What it is

rehuco-core is the non-GUI half of rehuco: everything the desktop editor needs to read and write a resource's .rehu sidecar, with no Qt dependency.

It provides:

  • Data models — the .rehu document, its common fields, and per-type plugin blocks
  • File I/O — atomic read and write, with unknown fields preserved verbatim
  • Format versioning — a per-file version, migrations applied on load, and read-only handling of a file written by a newer version
  • Content checksums — a .checksum record beside the .rehu holding, per content file, its hash, when it was last verified and what the answer was; generate and verify read it, and can re-check just one file or skip whatever was checked recently
  • Content enumeration — which files a resource covers, the images inside a reference pack's archives, and measured size on disk and video duration
  • A catalog — the .rehuco file naming folder roots, and the .rehudb SQLite cache of the records found under them: an incremental scan, targeted updates after a save or rename, and filtered reads
  • Staged images — an image taken out of a resource, written unchanged under a name that traces it back
  • A task queue — one long job at a time, pausable, cancellable, reorderable, optionally persisted across restarts
  • Legacy .tc conversion — parsing the predecessor format and converting it to .rehu, one file or a whole folder tree, with backups and rollback

Goals

rehuco-core aims to be:

  • MIT licensed — usable in open-source or closed-source projects freely
  • Dependency-light — no GUI dependencies; installable on headless servers and low-spec NAS hardware
  • Typed — fully annotated public API with a py.typed marker for type-checker integration

Installation

pip install rehuco-core

License

MIT

Metadata

Release files for rehuco-core 0.3.0

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

Source distribution (sdist)

Source distribution for rehuco-core 0.3.0
File Size Uploaded
rehuco_core-0.3.0.tar.gz 615.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rehuco-core 0.3.0
File Interpreter ABI Platform
rehuco_core-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 981.7 kB

Release files / rehuco_core-0.3.0.tar.gz

Download URL rehuco_core-0.3.0.tar.gz
Size 615.8 kB
Tags Source
SHA-256 checksum
How to use checksums
bb257a66e4c47b544e18d0243caeedd54de6dbdbe2a5067028249481785d9b82
BLAKE2b-256 checksum
How to use checksums
0691e7108065fec08c59aee8767caa4ea1d3f6990b2ea23a344705b2e1c790e6
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 Oct 11, 2026.

Transparency log

Release files / rehuco_core-0.3.0-py3-none-any.whl

Download URL rehuco_core-0.3.0-py3-none-any.whl
Size 365.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d1c6d376d7f6c4b8eb8fef218c09ab1bb4636f751f29c3ec2e5943376f48e39f
BLAKE2b-256 checksum
How to use checksums
8a9b0b8f20fc5d430dd14c417d2d6dfb5dee1ee055dcc6ed02e5ca7bde0abf3d
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 Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files

0.2.0

2 release files

0.1.0

2 release files

0.0.1

2 release files

0.0.0

2 release files

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