Skip to main content

zuu

Install

pip install zuu

Release behavior

Versions use a month-led form such as 202608.29.1, where the first component identifies the release month. A push to main publishes to PyPI automatically only when that component changes, such as from 202608 to 202609. Changes to the remaining components within the same month do not publish automatically. The publish workflow can still be run manually for any version.

Cases

Case Utility Purpose Depends on Documentation
case1 UserLevelHasher Store and check named hashes for composable filesystem inputs. case2 Guide
case2 FileSystemSnapshot Capture deterministic snapshots of files and directory trees. — Guide
case3 GitIgnorePlan Plan, apply, and verify Git-ignore coverage for selected paths. — Guide
case4 MarkdownTable Find, extract, compose, and replace Markdown pipe tables. — Guide
case5 ConfinedPath Treat paths like addresses inside a fenced property, keeping repository selection and exact target planning portable and confined. — Guide
case6 AffectedTargets Choose the smallest declared target set that safely covers changed repository paths. case5 Guide
case7 ProjectionPlan Plan updates to managed outputs without overwriting unowned or locally changed content. — Guide
case8 LayeredMapping Stack configuration like transparent sheets, letting later JSON and typed assignments cover earlier defaults without recursive merging. — Guide
case9 TemporaryJsonEnvironment Hand structured settings to child processes like a temporary luggage locker, using an environment path as the claim ticket and cleaning up afterward. — Guide
case10 TombstoneOverlay Personalize a shared mapping like a correction sheet, overlaying local values and crossed-out keys without changing the original. — Guide
case11 CliSelector Choose CLI values like a station clerk honoring tickets already in hand before opening a live terminal checklist. — Guide
case12 GitHubSubpath Synchronize an owned directory from a public GitHub repository subpath, using its resolved commit as the cache marker. case5 Guide
case13 deep_get Read, initialize, update, and remove nested values using item or attribute key paths. — Guide
case14 loads Read simple YAML configuration with nested mappings, lists, and scalar values. — Guide
case15 check_version Check cached GitHub configuration values for selected version changes. case13, case14 Guide

Metadata

Release files for zuu 202609.8.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 zuu 202609.8.0
File Size Uploaded
zuu-202609.8.0.tar.gz 41.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for zuu 202609.8.0
File Interpreter ABI Platform
zuu-202609.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 102.1 kB

Release files / zuu-202609.8.0.tar.gz

Download URL zuu-202609.8.0.tar.gz
Size 41.9 kB
Tags Source
SHA-256 checksum
How to use checksums
b1ebcf796f9d446211e775ad02f2f92258fdf4fb766fa8a3f4442e9ff422d505
BLAKE2b-256 checksum
How to use checksums
9a81bd433ea8efd48bcc23df4785b68b7d539f7e0f989ba771930232ac96af25
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 8, 2026.

Transparency log

Release files / zuu-202609.8.0-py3-none-any.whl

Download URL zuu-202609.8.0-py3-none-any.whl
Size 60.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f9de8bc75de6b5bef47354d81fd3f0b64ebf2db976ef4a751de749c171fcb454
BLAKE2b-256 checksum
How to use checksums
a658ae38dce8d2e5cf50d56f21e03c9d4abacbf3cf5225aa1a620bd9b0ce82b0
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 8, 2026.

Transparency log
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