heinzel-clock: the World Clock
What time it is for everyone on the team — a first-party Heinzelmännchen plugin, and the smallest plugin-owned feature: Python declarations, globe, assets and tests live in this project.
hz system plugin add clock --confirm
hz setup clock # pick the team's time zones and the working hours in each
hz clock # the team's local times; --json for agents
hz system config set clock.zones '[{ name = "Europe/Berlin", hours = [9, 18] }, "America/New_York"]'
Each zone is an IANA name, which gets working hours 9 to 18, or a table with its own hours. The same operation is
the MCP tool clock (hz system serve mcp) and GET /clock (hz system serve api); the zones are checked by
hz system doctor, and hz setup includes the World Clock's optional setup step.
The settings before per-zone hours (zones as names and one working_hours for all) are still read, and
hz system doctor reports them as degraded. hz setup clock rewrites them in the new shape when they are in your
user file; remove working_hours from a project hz.toml or HZ_CLOCK__WORKING_HOURS yourself.
Development and release commands: repository guide.
Migration provenance: heinzel, before the 0.9 plugin-boundary migration.
The fallback land outline is simplified Natural Earth land (public domain); representative zone points come from IANA's public-domain zone.tab. Bundled frontend dependency license notices are packaged alongside the built view.
Metadata
Release files for heinzel-clock 0.9.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| heinzel_clock-0.9.1.tar.gz | 141.0 kB | Without provenance | Details for heinzel_clock-0.9.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| heinzel_clock-0.9.1-py3-none-any.whl | Python 3 | none | any | Details for heinzel_clock-0.9.1-py3-none-any.whl |
Total release size: 180.6 kB
Release files / heinzel_clock-0.9.1.tar.gz
| Download URL | heinzel_clock-0.9.1.tar.gz |
|---|---|
| Size | 141.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd2fea8a4c0e5cfc54625d3558098e564e357c82324fcb6d078954a5944c1152
|
|
BLAKE2b-256 checksum How to use checksums |
9b7ec43342e61c921ad935e73322ac1d9dd96e5b7e4c0222b42197d071c37a11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / heinzel_clock-0.9.1-py3-none-any.whl
| Download URL | heinzel_clock-0.9.1-py3-none-any.whl |
|---|---|
| Size | 39.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0b64491bc470b381f6f08b0df218eee714cc75915b0c3aafdb3b6144e16bc0f
|
|
BLAKE2b-256 checksum How to use checksums |
16a032ca19abc980715fc2492898b75ffc875ca674f0001f36374e3fdf751004
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for heinzel-clock 0.9.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.