calprint 0.1.0

Print human-readable summaries of iCalendar (.ics) files.

calprint

calprint is a small Python CLI that reads an iCalendar (.ics) file and prints a human-readable summary of the calendar and its VEVENT entries.

It is intentionally simple:

• plain text output
• no recurrence expansion
• deterministic event ordering
• modern Python (>=3.12)
• uv-managed development workflow
• ruff formatting and linting
• ty type checking

Repository: https://github.com/schmidma/calprint

Issues: https://github.com/schmidma/calprint/issues

Install

Run once with uvx

uvx calprint path/to/calendar.ics

Install as a tool with uv

uv tool install calprint
calprint path/to/calendar.ics

Install with pip

pip install calprint
calprint path/to/calendar.ics

Usage

Console command

calprint path/to/calendar.ics

Module execution

python -m calprint path/to/calendar.ics

Version

calprint --version

Output

calprint prints:

• calendar name, version, product ID, and method
• timezone identifiers declared in VTIMEZONE
• total VEVENT count
• per-event summary, start, end, UID, organizer, attendees, location, and status

Missing optional values are rendered as -.

Dates and datetimes are formatted as:

• dates: YYYY-MM-DD
• naive datetimes: YYYY-MM-DD HH:MM
• timezone-aware datetimes: YYYY-MM-DD HH:MM TZ

Example

uv run calprint tests/fixtures/example_meeting.ics

Example output:

Calendar
  Name: -
  Version: 2.0
  Product ID: -//Example Industries//calprint//EN
  Method: REQUEST
  Timezones: Europe/Berlin
  Events: 1

Event 1
  Summary: Quarterly Roadmap Review and Planning Session
  Start: 2026-04-14 08:30 CEST
  End: 2026-04-14 09:30 CEST
  UID: [e-mail]
  Organizer: Taylor Example
  Attendees: Alex Example, Jordan Example
  Location: Virtual Meeting Room 3
  Status: CONFIRMED

Development

Create the project environment:

uv sync --dev

Run the CLI locally:

uv run calprint tests/fixtures/example_meeting.ics

Quality commands:

uv run ruff format .
uv run ruff format --check .
uv run ruff check .
uv run ty check src
uv run pytest

Build distributions:

uv build --no-sources

Test Fixtures

The repository includes a small fixture corpus under tests/fixtures/.

• synthetic meeting and invalid fixtures are safe to publish
• a few fixtures are adapted from the collective/icalendar test suite for interoperability coverage

See tests/fixtures/README.md for provenance details.

Releasing

Local release steps

1. Update the package version.

uv version 0.2.0

2. Run the local checks.

uv run ruff format --check .
uv run ruff check .
uv run ty check src
uv run pytest
uv build --no-sources

3. Commit the version bump.

4. Create and push a version tag.

git tag v0.2.0
git push origin v0.2.0

GitHub automation

Pushing a v* tag triggers the publish workflow, which will:

• validate that the tag matches project.version
• build the wheel and source distribution
• smoke-test both artifacts
• publish to PyPI with uv publish
• create a GitHub Release for the tag and attach the built artifacts

One-time publish setup

Before the publish workflow can succeed, configure:

1. a GitHub environment named pypi
2. a PyPI trusted publisher pointing at this repository and workflow

License

MIT

AI Assistance

This project was developed with support from AI coding agents. The repository, implementation plan, and code changes were produced collaboratively with AI-assisted development tools.