icalendar/docs/usage.rst

378 wiersze
11 KiB
ReStructuredText
Czysty Zwykły widok Historia

2005-03-23 14:10:49 +00:00
iCalendar package
=================
This package is used for parsing and generating iCalendar files following the
2005-03-23 14:10:49 +00:00
standard in RFC 2445.
It should be fully compliant, but it is possible to generate and parse invalid
2005-03-23 14:10:49 +00:00
files if you really want to.
2005-03-23 14:10:49 +00:00
File structure
--------------
An iCalendar file is a text file (utf-8) with a special format. Basically it
2005-03-23 14:10:49 +00:00
consists of content lines.
Each content line defines a property that has 3 parts (name, parameters,
2005-03-23 14:10:49 +00:00
values). Parameters are optional.
A simple content line with only name and value could look like this::
2005-03-23 14:10:49 +00:00
BEGIN:VCALENDAR
A content line with parameters can look like this::
2005-03-23 14:10:49 +00:00
ATTENDEE;CN=Max Rasmussen;ROLE=REQ-PARTICIPANT:MAILTO:example@example.com
2005-03-23 14:10:49 +00:00
And the parts are::
2005-03-23 14:10:49 +00:00
Name: ATTENDEE
Params: CN=Max Rasmussen;ROLE=REQ-PARTICIPANT
Value: MAILTO:example@example.com
Long content lines are usually "folded" to less than 75 character, but the
2005-03-23 14:10:49 +00:00
package takes care of that.
2005-03-23 14:10:49 +00:00
Overview
--------
On a higher level iCalendar files consists of components. Components can have
2005-03-23 14:10:49 +00:00
sub components.
The root component is the VCALENDAR::
2005-03-23 14:10:49 +00:00
BEGIN:VCALENDAR
... vcalendar properties ...
END:VCALENDAR
2005-03-23 14:10:49 +00:00
2005-03-23 17:05:32 +00:00
The most frequent subcomponent to a VCALENDAR is a VEVENT. They are
nested like this::
2005-03-23 14:10:49 +00:00
BEGIN:VCALENDAR
... vcalendar properties ...
BEGIN:VEVENT
... vevent properties ...
END:VEVENT
2005-03-23 14:10:49 +00:00
END:VCALENDAR
2005-03-23 17:05:32 +00:00
Inside the components there are properties with values. The values
have special types. Like integer, text, datetime etc. these values are
2005-03-23 17:05:32 +00:00
encoded in a special text format in an iCalendar file.
2005-03-23 14:10:49 +00:00
There are methods for converting to and from these encodings in the package.
2005-03-23 14:10:49 +00:00
These are the most important imports::
2005-03-23 14:10:49 +00:00
>>> from icalendar import Calendar, Event
2005-03-23 14:10:49 +00:00
2014-01-06 14:05:34 +00:00
Components
2005-03-23 14:10:49 +00:00
----------
Components are like (Case Insensitive) dicts. So if you want to set a property
you do it like this. The calendar is a component::
>>> cal = Calendar()
>>> cal['dtstart'] = '20050404T080000'
>>> cal['summary'] = 'Python meeting about calendaring'
>>> for k,v in cal.items():
... k,v
2022-10-11 09:03:49 +00:00
('DTSTART', '20050404T080000')
('SUMMARY', 'Python meeting about calendaring')
NOTE: the recommended way to add components to the calendar is to use
create the subcomponent and add it via Calendar.add! The example above adds a
string, but not a vText component.
2011-09-13 21:42:17 +00:00
You can generate a string for a file with the to_ical() method::
2011-09-13 21:42:17 +00:00
>>> cal.to_ical()
2022-10-11 09:03:49 +00:00
b'BEGIN:VCALENDAR\r\nDTSTART:20050404T080000\r\nSUMMARY:Python meeting about calendaring\r\nEND:VCALENDAR\r\n'
The rendered view is easier to read::
2005-03-23 14:10:49 +00:00
BEGIN:VCALENDAR
DTSTART:20050404T080000
SUMMARY:Python meeting about calendaring
END:VCALENDAR
2005-03-23 14:10:49 +00:00
2011-09-13 21:42:17 +00:00
So, let's define a function so we can easily display to_ical() output::
2005-03-23 14:10:49 +00:00
>>> def display(cal):
2022-10-11 09:03:49 +00:00
... return cal.to_ical().decode("utf-8").replace('\r\n', '\n').strip()
You can set multiple properties like this::
2005-03-23 14:10:49 +00:00
>>> cal = Calendar()
>>> cal['attendee'] = ['MAILTO:maxm@mxm.dk','MAILTO:test@example.com']
2022-10-11 09:03:49 +00:00
>>> print(display(cal))
BEGIN:VCALENDAR
ATTENDEE:MAILTO:maxm@mxm.dk
ATTENDEE:MAILTO:test@example.com
END:VCALENDAR
2005-03-23 14:10:49 +00:00
If you don't want to care about whether a property value is a list or
a single value, just use the add() method. It will automatically
convert the property to a list of values if more than one value is
added. Here is an example::
2005-03-23 14:10:49 +00:00
>>> cal = Calendar()
>>> cal.add('attendee', 'MAILTO:maxm@mxm.dk')
>>> cal.add('attendee', 'MAILTO:test@example.com')
2022-10-11 09:03:49 +00:00
>>> print(display(cal))
BEGIN:VCALENDAR
ATTENDEE:MAILTO:maxm@mxm.dk
ATTENDEE:MAILTO:test@example.com
END:VCALENDAR
2005-03-23 14:10:49 +00:00
Note: this version doesn't check for compliance, so you should look in
the RFC 2445 spec for legal properties for each component, or look in
the icalendar/calendar.py file, where it is at least defined for each
component.
2005-03-23 14:10:49 +00:00
2005-03-23 14:10:49 +00:00
Subcomponents
-------------
2005-03-23 17:05:32 +00:00
Any component can have subcomponents. Eg. inside a calendar there can
be events. They can be arbitrarily nested. First by making a new
component::
2005-03-23 14:10:49 +00:00
>>> event = Event()
>>> event['uid'] = '42'
>>> event['dtstart'] = '20050404T080000'
2005-03-23 14:10:49 +00:00
And then appending it to a "parent"::
2005-03-23 14:10:49 +00:00
>>> cal.add_component(event)
2022-10-11 09:03:49 +00:00
>>> print(display(cal))
BEGIN:VCALENDAR
ATTENDEE:MAILTO:maxm@mxm.dk
ATTENDEE:MAILTO:test@example.com
BEGIN:VEVENT
DTSTART:20050404T080000
UID:42
END:VEVENT
END:VCALENDAR
2005-03-23 14:10:49 +00:00
Subcomponents are appended to the subcomponents property on the component::
2005-03-23 14:10:49 +00:00
>>> cal.subcomponents
2022-10-11 09:03:49 +00:00
[VEVENT({'UID': '42', 'DTSTART': '20050404T080000'})]
2005-03-23 14:10:49 +00:00
Value types
-----------
Property values are utf-8 encoded strings.
2005-03-23 17:05:32 +00:00
This is impractical if you want to use the data for further
computation. The datetime format for example looks like this:
'20050404T080000'. But the package makes it simple to parse and
2005-03-23 17:05:32 +00:00
generate iCalendar formatted strings.
2005-03-23 14:10:49 +00:00
Basically you can make the add() method do the thinking, or you can do it
2005-03-23 14:10:49 +00:00
yourself.
2005-03-23 17:05:32 +00:00
To add a datetime value, you can use Pythons built in datetime types,
and the set the encode parameter to true, and it will convert to the
type defined in the spec::
2005-03-23 14:10:49 +00:00
>>> from datetime import datetime
>>> cal.add('dtstart', datetime(2005,4,4,8,0,0))
2011-09-13 21:42:17 +00:00
>>> cal['dtstart'].to_ical()
2022-10-11 09:03:49 +00:00
b'20050404T080000'
If that doesn't work satisfactorily for some reason, you can also do it
2005-03-23 14:10:49 +00:00
manually.
2005-03-23 17:05:32 +00:00
In 'icalendar.prop', all the iCalendar data types are defined. Each
type has a class that can parse and encode the type.
2005-03-23 14:10:49 +00:00
So if you want to do it manually::
2005-03-23 14:10:49 +00:00
>>> from icalendar import vDatetime
>>> now = datetime(2005,4,4,8,0,0)
2011-09-13 21:42:17 +00:00
>>> vDatetime(now).to_ical()
2022-10-11 09:03:49 +00:00
b'20050404T080000'
2005-03-23 14:10:49 +00:00
2005-03-23 17:05:32 +00:00
So the drill is to initialise the object with a python built in type,
2011-09-13 21:42:17 +00:00
and then call the "to_ical()" method on the object. That will return an
2005-03-23 17:05:32 +00:00
ical encoded string.
2005-03-23 14:10:49 +00:00
You can do it the other way around too. To parse an encoded string, just call
the "from_ical()" method, and it will return an instance of the corresponding
Python type::
2005-03-23 14:10:49 +00:00
>>> vDatetime.from_ical('20050404T080000')
datetime.datetime(2005, 4, 4, 8, 0)
2005-03-23 14:10:49 +00:00
>>> dt = vDatetime.from_ical('20050404T080000Z')
>>> repr(dt)[:62]
'datetime.datetime(2005, 4, 4, 8, 0, tzinfo=<UTC>)'
2005-03-23 14:10:49 +00:00
You can also choose to use the decoded() method, which will return a decoded
value directly::
2005-03-23 14:10:49 +00:00
>>> cal = Calendar()
>>> cal.add('dtstart', datetime(2005,4,4,8,0,0))
2011-09-13 21:42:17 +00:00
>>> cal['dtstart'].to_ical()
2022-10-11 09:03:49 +00:00
b'20050404T080000'
>>> cal.decoded('dtstart')
datetime.datetime(2005, 4, 4, 8, 0)
2005-03-23 14:10:49 +00:00
Property parameters
-------------------
Property parameters are automatically added, depending on the input value. For
example, for date/time related properties, the value type and timezone
identifier (if applicable) are automatically added here::
2022-10-11 09:03:49 +00:00
>>> import pytz
>>> event = Event()
>>> event.add('dtstart', datetime(2010, 10, 10, 10, 0, 0,
... tzinfo=pytz.timezone("Europe/Vienna")))
>>> lines = event.to_ical().splitlines()
2022-10-11 09:03:49 +00:00
>>> assert (
2022-11-03 18:41:17 +00:00
... b"DTSTART;TZID=Europe/Vienna:20101010T100000"
... in lines)
You can also add arbitrary property parameters by passing a parameters
dictionary to the add method like so::
>>> event = Event()
>>> event.add('X-TEST-PROP', 'tryout.',
... parameters={'prop1':'val1', 'prop2':'val2'})
>>> lines = event.to_ical().splitlines()
2022-10-11 09:03:49 +00:00
>>> assert b"X-TEST-PROP;PROP1=val1;PROP2=val2:tryout." in lines
2005-03-23 14:10:49 +00:00
Example
-------
2005-03-23 17:05:32 +00:00
Here is an example generating a complete iCal calendar file with a
single event that can be loaded into the Mozilla calendar.
2005-03-23 14:10:49 +00:00
Init the calendar::
>>> cal = Calendar()
>>> from datetime import datetime
>>> import pytz
Some properties are required to be compliant::
>>> cal.add('prodid', '-//My calendar product//mxm.dk//')
>>> cal.add('version', '2.0')
We need at least one subcomponent for a calendar to be compliant::
2012-08-24 11:06:40 +00:00
>>> event = Event()
>>> event.add('summary', 'Python meeting about calendaring')
>>> event.add('dtstart', datetime(2005,4,4,8,0,0,tzinfo=pytz.utc))
>>> event.add('dtend', datetime(2005,4,4,10,0,0,tzinfo=pytz.utc))
>>> event.add('dtstamp', datetime(2005,4,4,0,10,0,tzinfo=pytz.utc))
A property with parameters. Notice that they are an attribute on the value::
>>> from icalendar import vCalAddress, vText
>>> organizer = vCalAddress('MAILTO:noone@example.com')
Automatic encoding is not yet implemented for parameter values, so you
must use the 'v*' types you can import from the icalendar package
(they're defined in ``icalendar.prop``)::
>>> organizer.params['cn'] = vText('Max Rasmussen')
>>> organizer.params['role'] = vText('CHAIR')
>>> event['organizer'] = organizer
>>> event['location'] = vText('Odense, Denmark')
>>> event['uid'] = '20050115T101010/27346262376@mxm.dk'
>>> event.add('priority', 5)
>>> attendee = vCalAddress('MAILTO:maxm@example.com')
>>> attendee.params['cn'] = vText('Max Rasmussen')
>>> attendee.params['ROLE'] = vText('REQ-PARTICIPANT')
>>> event.add('attendee', attendee, encode=0)
>>> attendee = vCalAddress('MAILTO:the-dude@example.com')
>>> attendee.params['cn'] = vText('The Dude')
>>> attendee.params['ROLE'] = vText('REQ-PARTICIPANT')
>>> event.add('attendee', attendee, encode=0)
Add the event to the calendar::
>>> cal.add_component(event)
By extending the event with subcomponents, you can create multiple alarms::
>>> from icalendar import Alarm
>>> from datetime import timedelta
>>> alarm_1h_before = Alarm()
>>> alarm_1h_before.add('action', 'DISPLAY')
>>> alarm_1h_before.add('trigger', timedelta(hours=-1))
>>> alarm_1h_before.add('description', 'Reminder: Event in 1 hour')
>>> event.add_component(alarm_1h_before)
>>> alarm_24h_before = Alarm()
>>> alarm_24h_before.add('action', 'DISPLAY')
>>> alarm_24h_before.add('trigger', timedelta(hours=-24))
>>> alarm_24h_before.add('description', 'Reminder: Event in 24 hours')
>>> event.add_component(alarm_24h_before)
Or even recurrence::
>>> event.add('rrule', {'freq': 'daily'})
Write to disk::
>>> import tempfile, os
>>> directory = tempfile.mkdtemp()
>>> f = open(os.path.join(directory, 'example.ics'), 'wb')
2011-09-13 21:42:17 +00:00
>>> f.write(cal.to_ical())
2024-05-01 18:05:24 +00:00
733
>>> f.close()
Print out the calendar::
>>> print(cal.to_ical().decode('utf-8')) # doctest: +NORMALIZE_WHITESPACE
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//My calendar product//mxm.dk//
BEGIN:VEVENT
SUMMARY:Python meeting about calendaring
DTSTART:20050404T080000Z
DTEND:20050404T100000Z
DTSTAMP:20050404T001000Z
UID:20050115T101010/27346262376@mxm.dk
RRULE:FREQ=DAILY
ATTENDEE;CN="Max Rasmussen";ROLE=REQ-PARTICIPANT:MAILTO:maxm@example.com
ATTENDEE;CN="The Dude";ROLE=REQ-PARTICIPANT:MAILTO:the-dude@example.com
LOCATION:Odense\, Denmark
ORGANIZER;CN="Max Rasmussen";ROLE=CHAIR:MAILTO:noone@example.com
PRIORITY:5
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:Reminder: Event in 1 hour
TRIGGER:-PT1H
END:VALARM
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:Reminder: Event in 24 hours
TRIGGER:-P1D
END:VALARM
END:VEVENT
END:VCALENDAR
<BLANKLINE>
2005-03-23 14:10:49 +00:00
More documentation
==================
Have a look at the `tests <https://github.com/collective/icalendar/tree/master/src/icalendar/tests>`__ of this package to get more examples.
All modules and classes docstrings, which document how they work.