Skip to main content

timeglance

Python tests pre-commit Ruff pip-audit bandit Last commit License PyPI version Downloads sigstore OSSF Scorecard

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

  • Weekly - your routine sheet with topic 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.

One web control panel drives both - preview live, toggle layers, edit the YAML, export, or set the wallpaper:

The weekly routine in the control panel

The year planner in the control panel

...and the rendered output you print or set as a wallpaper:

Weekly routine sheet

Year-at-a-glance planner

Try it instantly (Docker)

The zero-install way to see the control panel and renders - a test drive, not a deployment target. A container can't reach your desktop session, so Docker can never set the wallpaper (the UI auto-hides it, and a scheduled "set wallpaper" renders the file but skips the set). Bridging the host display/DBus into a container isn't something we intend to solve - to actually use timeglance on your desktop, install it locally (next section).

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.

Install (Ubuntu/Debian)

The simplest way on a Debian-based desktop. Grab the .deb from the latest release and install it - apt pulls every dependency (the Python libraries, poppler, native Cairo/Pango stack, tray AppIndicator, fonts) from your distro:

sudo apt install ./timeglance_<version>_all.deb

Then launch timeglance from your applications menu - the tray icon appears and opens the control panel, no terminal needed. Or drive it from the CLI (timeglance is now on your PATH):

timeglance init     # scaffold year/ + weekly/ config.yaml from the templates
timeglance serve    # the control panel at http://localhost:8753

A pure-Python install under /usr/lib/python3/dist-packages run by your system Python, with every dependency satisfied by your distro's own apt packages. CI builds and install-tests the .deb on Ubuntu 24.04, 25.10 and 26.04; other recent releases may work.

Uninstalling. timeglance sets up user-level bits that apt can't remove: a systemd timer for the daily render and, if you enabled it, a tray autostart entry. Run timeglance uninstall first - it stops a running tray, disables the timer, and removes both the unit files and the autostart entry - then sudo apt remove timeglance. Your per-user configs and output (~/.config/timeglance, ~/.local/state/timeglance, ~/.local/share/timeglance) are left untouched either way.

Install (Python/uv)

Needs Python 3.12+ and uv. WeasyPrint and CairoSVG load native libraries (Cairo, Pango, GDK-PixBuf) at runtime, and the wallpaper feature rasterizes the sheet with poppler's pdftocairo; 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 poppler-utils
uv sync
uv run timeglance init      # scaffold year/ + weekly/ config.yaml from the templates
uv run timeglance serve     # the control panel at http://localhost:8753

Config, state and rendered output live under the XDG base directories by default (~/.config/timeglance, ~/.local/state/timeglance, ~/.local/share/timeglance); set TIMEGLANCE_HOME=$PWD to keep it all in the current folder instead.

Headless renders (each flag has a YAML equivalent):

uv run timeglance render year --theme light --layout vertical   # render the year planner
uv run timeglance render weekly --format both                   # render the weekly sheet

Set and forget (systemd timer)

To re-render (and optionally re-wallpaper) on a schedule with nothing running and nothing to start after a reboot:

timeglance install              # write a user service + timer and enable it now
timeglance install --time 06:30 # or pick the time (default: schedule.yaml's)
timeglance uninstall            # remove it

(From a source checkout, prefix these with uv run.) This drops timeglance-render.service (a oneshot that runs timeglance run, honouring your schedule.yaml) and timeglance-render.timer into ~/.config/systemd/user/, then enables the timer. Persistent=true means a run missed while the machine was off happens on the next boot. Change the time by re-running timeglance install --time HH:MM.

Setting the Plasma wallpaper needs an active graphical session, so a render while you're fully logged out writes the files but can't paint - it repaints on your next session. For renders while logged out (no wallpaper), enable lingering: loginctl enable-linger $USER.

Tray controller

A system-tray menu to open the panel and flip the schedule - a launcher and quick toggles, not the scheduler (the timer above keeps running whether or not the tray is open).

The .deb already includes it: after apt install, launch timeglance from your applications menu and the tray icon appears (it pulls the system AppIndicator/GObject libraries as dependencies). From a source checkout, add the extra and the system libraries, then run it:

sudo apt install python3-gi gir1.2-ayatanaappindicator3-0.1
uv sync --extra tray
uv run timeglance tray

The menu opens the control panel (starting the server first if needed), starts/stops it, picks the port, and toggles the schedule: enabled, time, which planners render, and which set the wallpaper. Autostart adds an XDG autostart entry so the tray is there every session (the same thing KDE's System Settings → Autostart manages). Quitting the tray only closes the panel it started - the systemd timer keeps running regardless.

Docs

Metadata

Release files for timeglance 3.4.2

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 3.4.2
File Size Uploaded
timeglance-3.4.2.tar.gz 595.2 kB Details

Built distribution (wheel)

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

Total release size: 685.3 kB

Release files / timeglance-3.4.2.tar.gz

Download URL timeglance-3.4.2.tar.gz
Size 595.2 kB
Tags Source
SHA-256 checksum
How to use checksums
a2d96e19ad8a786bc0d0eb35b9ee689c36c9426879015d2a1ea55cd57eb2256d
BLAKE2b-256 checksum
How to use checksums
dce286d44257420f0163b11cc876e5bfe17d017af8c868673ba2d8bd2df1e11f
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 13, 2026.

Transparency log

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

Download URL timeglance-3.4.2-py3-none-any.whl
Size 90.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ad8b43ff6fcc7beb6b5b9b9355949ae785b86ea5154512bae39986eb3e6726f2
BLAKE2b-256 checksum
How to use checksums
51453230440bc8807e70cd3d5bdbebc82dca9419c1b1d0704ebc027fd7207a4e
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 13, 2026.

Transparency log

Release history Release notifications | RSS feed

3.5.3

2 release files

3.5.2

2 release files

3.5.1

2 release files

This release

3.4.2 This release

2 release files

3.4.1

2 release files

3.4.0

2 release files

3.3.5

2 release files

3.3.4

2 release files

3.3.3

2 release files

3.3.2

2 release files

3.2.1

2 release files

3.2.0

2 release files

3.1.0

2 release files

3.0.0

2 release files

2.0.0

2 release files

1.3.0

2 release files

1.2.0

2 release files

1.1.2

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.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