YAML to iCalendar (ics)
| WARNING: this project is still in beta. Beware of breaking changes! |
|---|
Convert YAML files to .ics files which can be imported into other calendar applications.
Features include:
- Converting single .yaml files, or combining multiple into one .ics file.
- ics fields: name, summary, description, location, timezone, repeat
- Specify event start+end or start+duration
- Recurring events (basic support)
- All-day events
- Timezone specification (default or per-event)
Installation
pip install yaml2ics
Usage
To produce a calendar from a list of events:
python yaml2ics.py example/test_calendar.yaml
To combine lists of events in to a calendar:
python yaml2ics.py example/test_calendar.yaml example/another_calendar.yaml
Syntax
Please see example/test_calendar.yaml for a full demo including
explanations. Below is a minimal template that shows the basic idea:
name: Calendar Name
timezone: Europe/Helsinki # default timezone for events, optional
events:
- summary: The event title
begin: 2021-09-21 15:00:00
duration:
minutes: 30
location: |
https://meet.jit.si/example
description: |
In this meeting we will ...
Timezones
The event timezone can be specified in three ways (in reverse order of precedence):
-
Using the
timezone: ...field, as shown above under "Syntax". -
Adding it to an individual event:
- summary: My event timezone: America/Los_Angeles
-
By specifying a timezone in the event start time:
2021-09-21 15:00:00 +07:00
Valid timezones are listed at https://datetime.app/iana-timezones
If no timezone is set, we default to UTC.
Contributing
Contributions are welcomed! This project is still in active development and should be considered beta.
To install the development version, fork the source of the project and make an editable install:
pip install -e ".[test]"
To test:
pytest
Generate a coverage report with:
pytest --cov-report term-missing --cov yaml2ics
black and other linters are used to auto-format
files (and enforced by CI). To install the git hooks, use pre-commit install.
To run the tests/auto-formatting manually, use pre-commit run --all-files.
Release files for yaml2ics 0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| yaml2ics-0.3.tar.gz | 15.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| yaml2ics-0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.6 kB
Release files / yaml2ics-0.3.tar.gz
| Download URL | yaml2ics-0.3.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4faa4130f756ef805792a9a389599e78830731afadf4383340a68e42af28d6d7
|
|
BLAKE2b-256 checksum How to use checksums |
137b45b0da7497f3bce402d13a5206335bef1a2e608c5e420f1694394aa4b095
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 4, 2025.
Transparency logRelease files / yaml2ics-0.3-py3-none-any.whl
| Download URL | yaml2ics-0.3-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bcfa6dd783a2912c4454bf3baa5f80dcc725820b6b02cc776f0f34142906d50
|
|
BLAKE2b-256 checksum How to use checksums |
1298f33bd6bba7af1837865c36eaf64afdfa04062d8ba39c2b8c90c2fb95b559
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 4, 2025.
Transparency log