Skip to main content

timeglance

Python tests pre-commit Ruff pip-audit bandit Last commit License

Config-driven time planning at a glance - one web UI controls two tools:

  • Weekly - your routine sheet with activity layers. Print it or set it as a desktop wallpaper.
  • Year - a wide year-at-a-glance planner, with layers fed by your own calendars, public holidays, and manually added events. Print it or set it as a desktop wallpaper.

Weekly routine sheet

Year-at-a-glance planner

Quick start (Docker)

docker compose run --rm timeglance timeglance-init   # first run: scaffold year/ + weekly/ config.yaml
docker compose up                                    # then open http://localhost:8753

Config, outputs and scheduler state are bind-mounted under ./year, ./weekly and ./state, so the UI edits files on your host. Outputs are written as your host user — the compose file defaults to 1000:1000 (the usual first Linux user), so it just works for most; if your uid differs, run UID=$(id -u) GID=$(id -g) docker compose up.

Wallpaper-setting needs a live Plasma session, so it works only with the local install (next section), not in Docker; the container UI auto-hides it.

Quick start (local)

Needs Python 3.13 and uv. WeasyPrint and CairoSVG load native libraries (Cairo, Pango, GDK-PixBuf) at runtime; most Linux desktops already have these, but on a minimal or server install add them first (Debian/Ubuntu):

sudo apt-get install libcairo2 libpango-1.0-0 libpangocairo-1.0-0 libgdk-pixbuf-2.0-0
uv sync
uv run timeglance-init     # scaffold year/ + weekly/ config.yaml from the templates
uv run timeglance          # the control panel at http://localhost:8753

Headless renders (each flag has a YAML equivalent):

uv run timeglance-year --theme light --layout vertical   # -> year/out/
uv run timeglance-weekly --format both                   # -> weekly/out/

Docs

Limitations

  • Wallpaper-setting is host-only. The container can't reach a Plasma session, so inside Docker the feature self-hides and a scheduled "set wallpaper" renders the files but skips the set (logged as wallpaper skipped (no backend)). Run the server/CLI on the host to set wallpapers.
  • Weekly blocks can't overlap in time. Two activities over the same slot on the same day render on top of each other, so only one reads clearly.

Metadata

Release files for timeglance 1.0.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 timeglance 1.0.0
File Size Uploaded
timeglance-1.0.0.tar.gz 423.0 kB Details

Built distribution (wheel)

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

Total release size: 483.6 kB

Release files / timeglance-1.0.0.tar.gz

Download URL timeglance-1.0.0.tar.gz
Size 423.0 kB
Tags Source
SHA-256 checksum
How to use checksums
74f8b1d87819e9a89077b554863ee29ac8e5a9dab720df4b248a8bfae8ce56a2
BLAKE2b-256 checksum
How to use checksums
9c95edcf415581450fb241fef8b5608ddea3fa830bc078951aea41bae408cb62
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 3, 2026.

Transparency log

Release files / timeglance-1.0.0-py3-none-any.whl

Download URL timeglance-1.0.0-py3-none-any.whl
Size 60.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
948246468ef76edb0e520c9d39310cad5480c528d82d4c37efd820d251ef16af
BLAKE2b-256 checksum
How to use checksums
02e37fb03934e783146d7d7b63e51139e8ad598123c593e24eb02f1e42148c86
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 3, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

This release

1.0.0 This release

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