+ jtD a0t$Rt^RIHt^RIt^RIHtHtHt^RIH t H t H t ^RI H t HtHtHtHt^RIHtHt^RIHt^RIHtHtHtHtHtHtHtHtH t H!t!^R I"H#t#^R I$H%t%^R I&H't'^R I(H)t)] 'd^R I*H+t+H,t,^RI-H.t.RRlt/RRlt0RRlt1]2!]/]0]14t3RRlt4RRlt5RRlt6]2!]4]5]64t7RRlt8]2!]84t9RRlt:RR/R R!llt;R"R#lt];!R)^R*^R+7t?R,R-lt@R.R/ltAR0R1ltB]2!]@]A]BR24tCR3R4ltDR5R6ltER7R8ltF]2!]D]E]FR94tG]=!R:R;4tH]:!RRR?4tJ]R3R@RAlltK]RQ4tT]S!RRRS4tU]K!RTRU]]3]],RV]4tVRWRXltWRYRZltXR[R\ltY]2!]W]X]Y4tZR]R^lt[][!R_] ] PR`4t]RaRblt^]^!4t_];!Rc^Rd^R+7t`][!Re]]PRf4tb][!Rg]]PRh4td][!Ri]R$Rj4te]=!RkRl4tf]=!RmRn4tg]:!RoRRp4th]S!RqRr4tiRsRtltj]j!RuRv4tk]j!RwRx4tl]2RyRzl4tm]2R{R|l4tn]nPR}R~l4tn]nPR4tnRRltqRRltrRRltsRRlttRRltuRRltvRRltwRRltx]2!]x4tyRRltzRRlt{RRlt|]2!]z]{]|4t}RRlt~]] ,],]!,R,]]] ,],]!,,,tR]R&RRltRRlt]2!]~]]4tR],],] ,],]]],] ,],,,tR]R&RRltRRltRRlt]2!]]]4tRRlt]] ],,],] ,R,tR]R&RRltRRlt]2!]]]4tRRlt]!RR4t]!RR4t.RNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNtR#)z(Attributes of Components and properties.) annotationsN)datedatetime timedelta) TYPE_CHECKINGLiteral TypeAlias)BUSYTYPECLASSSTATUSTRANSPStrEnum)IncompleteComponentInvalidCalendar)SEQUENCE_TYPES) vCalAddress vCategory vDDDTypes vDurationvRecurvTextvUidvUnknownvUri vXmlReference) Conference)Image)tzp)is_date)CallableSequence) Componentc V^8dQhRRRR/#)selfr!returnzKlist[tuple[date, None] | tuple[datetime, None] | tuple[datetime, datetime]])formats"M/home/ralf/ical-fahrzeuge/venv/lib/python3.14/site-packages/icalendar/attr.py __annotate__r)#s ]] ]P]c.pVPR.4p\V\4'gV3MTFpVPFpVPp\V\ 4'db\V^,\ 4'd2VPV^,V^,V^,,34KsVPV4KVPVR34K K V#)ac The RDATE property defines the list of DATE-TIME values for recurring components. RDATE is defined in :rfc:`5545`. The return value is a list of tuples ``(start, end)``. ``start`` can be a :class:`datetime.date` or a :class:`datetime.datetime`, with and without timezone. ``end`` is :obj:`None` if the end is not specified and a :class:`datetime.datetime` if the end is specified. Value Type: The default value type for this property is DATE-TIME. The value type can be set to DATE or PERIOD. Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property. Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component. Description: This property can appear along with the "RRULE" property to define an aggregate set of repeating occurrences. When they both appear in a recurring component, the recurrence instances are defined by the union of occurrences defined by both the "RDATE" and "RRULE". The recurrence dates, if specified, are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE-TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored. Example: Below, we set one RDATE in a list and get the resulting tuple of start and end. .. code-block:: pycon >>> from icalendar import Event >>> from datetime import datetime >>> event = Event() # Add a list of recurrence dates >>> event.add("RDATE", [datetime(2025, 4, 28, 16, 5)]) >>> event.rdates [(datetime.datetime(2025, 4, 28, 16, 5), None)] .. note:: Modifying the returned list does not change the RDATE value. Assign to :attr:`rdates` or use :func:`icalendar.cal.Component.add` instead. If you want to compute recurrences, have a look at `Related Projects `_. RDATEN)get isinstancelistdtsdttuplerappend)r$resultrdatesr0rdates& r( _get_rdatesr7#s^F XXgr "F#-fd#;#;6)G::CFFE%''eAh 22MM58U1Xa-@"ABMM%( udm,H Mr*c V^8dQhRRRR/#r#r$r!r%Noner&)r's"r(r)r)s ! !i !4 !r*cT\V4V'dVPRV4R#R#)zSet the RDATE values, replacing any existing ones. ``value`` is a list as returned by :attr:`rdates` (each item a date, a datetime, or a ``(start, end)`` period tuple). Setting an empty list or :obj:`None` removes the RDATE property. r,N) _del_rdatesaddr$values&&r( _set_rdatesr@s"  %  r*c V^8dQhRRRR/#r9r&)r's"r(r)r)siDr*c*VPRR4R#)zDelete all RDATE values.r,Npopr$s&r(r<r<sHHWdr*c V^8dQhRRRR/#)r#r$r!r%zlist[date | datetime]r&)r's"r(r)r)sMMyM%:Mr*c.pVPR.4p\V\4'gV3MTF3pVPF pVPpVP V4K" K5 V#)ak EXDATE defines the list of DATE-TIME exceptions for recurring components. EXDATE is defined in :rfc:`5545`. Value Type: The default value type for this property is DATE-TIME. The value type can be set to DATE. Property Parameters: IANA, non-standard, value data type, and time zone identifier property parameters can be specified on this property. Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component. Description: The exception dates, if specified, are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE-TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). When duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored. The "EXDATE" property can be used to exclude the value specified in "DTSTART". However, in such cases, the original "DTSTART" date MUST still be maintained by the calendaring and scheduling system because the original "DTSTART" value has inherent usage dependencies by other properties such as the "RECURRENCE-ID". Example: Below, we add an exdate in a list and get the resulting list of exdates. .. code-block:: pycon >>> from icalendar import Event >>> from datetime import datetime >>> event = Event() # Add a list of excluded dates >>> event.add("EXDATE", [datetime(2025, 4, 28, 16, 5)]) >>> event.exdates [datetime.datetime(2025, 4, 28, 16, 5)] .. note:: Modifying the returned list does not change the EXDATE value. Assign to :attr:`exdates` or use :func:`icalendar.cal.Component.add` instead. If you want to compute recurrences, have a look at `Related Projects `_. EXDATE)r-r.r/r0r1r3)r$r4exdatesr0exdates& r( _get_exdatesrKsbLFhhx$G%/%>%>G:GK;;CVVF MM& !L Mr*c V^8dQhRRRR/#r9r&)r's"r(r)r)s""y"D"r*cT\V4V'dVPRV4R#R#)zSet the EXDATE values, replacing any existing ones. ``value`` is a list as returned by :attr:`exdates` (each item a date or a datetime). Setting an empty list or :obj:`None` removes the EXDATE property. rHN) _del_exdatesr=r>s&&r( _set_exdatesrOs"   5! r*c V^8dQhRRRR/#r9r&)r's"r(r)r)syTr*c*VPRR4R#)zDelete all EXDATE values.rHNrCrEs&r(rNrNsHHXtr*c V^8dQhRRRR/#)r#r$r!r%z list[vRecur]r&)r's"r(r)r)smmimLmr*c\VPR.4p\V\4'gV.#V#)aRRULE defines a rule or repeating pattern for recurring components. RRULE is defined in :rfc:`5545`. :rfc:`7529` adds the ``SKIP`` parameter :class:`icalendar.prop.vSkip`. Property Parameters: IANA and non-standard property parameters can be specified on this property. Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component, but it SHOULD NOT be specified more than once. The recurrence set generated with multiple "RRULE" properties is undefined. Description: The recurrence rule, if specified, is used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD be synchronized with the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value not synchronized with the recurrence rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE- TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored. The "DTSTART" property specified within the iCalendar object defines the first instance of the recurrence. In most cases, a "DTSTART" property of DATE-TIME value type used with a recurrence rule, should be specified as a date with local time and time zone reference to make sure all the recurrence instances start at the same local time regardless of time zone changes. If the duration of the recurring component is specified with the "DTEND" or "DUE" property, then the same exact duration will apply to all the members of the generated recurrence set. Else, if the duration of the recurring component is specified with the "DURATION" property, then the same nominal duration will apply to all the members of the generated recurrence set and the exact duration of each recurrence instance will depend on its specific start time. For example, recurrence instances of a nominal duration of one day will have an exact duration of more or less than 24 hours on a day where a time zone shift occurs. The duration of a specific recurrence may be modified in an exception component or simply by using an "RDATE" property of PERIOD value type. Examples: Daily for 10 occurrences: .. code-block:: pycon >>> from icalendar import Event >>> from datetime import datetime >>> from zoneinfo import ZoneInfo >>> event = Event() >>> event.start = datetime(1997, 9, 2, 9, 0, tzinfo=ZoneInfo("America/New_York")) >>> event.add("RRULE", "FREQ=DAILY;COUNT=10") >>> print(event.to_ical()) BEGIN:VEVENT DTSTART;TZID=America/New_York:19970902T090000 RRULE:FREQ=DAILY;COUNT=10 END:VEVENT >>> event.rrules [vRecur({'FREQ': ['DAILY'], 'COUNT': [10]})] Daily until December 24, 1997: .. code-block:: pycon >>> from icalendar import Event, vRecur >>> from datetime import datetime >>> from zoneinfo import ZoneInfo >>> event = Event() >>> event.start = datetime(1997, 9, 2, 9, 0, tzinfo=ZoneInfo("America/New_York")) >>> event.add("RRULE", vRecur({"FREQ": ["DAILY"]}, until=datetime(1997, 12, 24, tzinfo=ZoneInfo("UTC")))) >>> print(event.to_ical()) BEGIN:VEVENT DTSTART;TZID=America/New_York:19970902T090000 RRULE:FREQ=DAILY;UNTIL=19971224T000000Z END:VEVENT >>> event.rrules [vRecur({'FREQ': ['DAILY'], 'UNTIL': [datetime.datetime(1997, 12, 24, 0, 0, tzinfo=ZoneInfo(key='UTC'))]})] .. note:: You cannot modify the RRULE value by modifying the result. Use :func:`icalendar.cal.Component.add` to add values. If you want to compute recurrences, have a look at `Related Projects `_. RRULEr-r.r/)r$rruless& r( _get_rrulesrWs.TXXgr "F fd # #x Mr*c(V^8dQhRRRRRRRR/#)r# main_propstrcompatibility_prop str | Nonedocr%propertyr&)r's"r(r)r)ms,&+&+&+(2&+9<&+ &+r*c`aaaRVV3RllpRVVV3RllpRVV3Rllo\W4SV4#)a>This creates a text property. This property can be defined several times with different ``LANGUAGE`` parameters. Parameters: main_prop (str): The property to set and get, such as ``NAME`` compatibility_prop (str): An old property used before, such as ``X-WR-CALNAME`` doc (str): The documentation string c V^8dQhRRRR/#)r#r$r!r%r\r&)r's"r(r)2multi_language_text_property..__annotate__zs  9  r*c<VPS4pVfSeVPS4p\V\4'dVFpRVP9gKVu# V#)Get the propertyLANGUAGE)r-r.r/params)r$r4itemr[rYs& r(fget*multi_language_text_property..fgetzsZ)$ >0<XX01F fd # #T[[0K r*c V^8dQhRRRR/#r#r$r!r?r\r&)r's"r(r)ras4494Z4r*cx<S!V4Ve-VPSV4SeVPSV4R#R#R#)Set the property.Nr=)r$r?r[fdelrYs&&r(fset*multi_language_text_property..fsets= T   HHY &!-+U3. r*cV^8dQhRR/#r#r$r!r&)r's"r(r)ras//9/r*c\<VPSR4SeVPSR4R#R#zDelete the property.NrC)r$r[rYs&r(rn*multi_language_text_property..fdels+ D!  ) HH' . *r*r^)rYr[r]rgrornsff& @r(multi_language_text_propertyrwms2  44// Dc **r* min_valuec ,V^8dQhRRRRRRRRRR /#) r#proprZdefaultintr]rx int | Noner%r^r&)r's"r(r)r)s4%+%+ %+%+"%%+5?%+ %+r*c`aaaaRVV3RllpRVVV3RllpRV3Rllo\WESV4#)a]Create a property for an int value that exists only once. Parameters: default: Required. The default value. doc: Required. The documentation string. prop: Required. The name of the property. min_value: If set, the value must be greater than or equal to this minimum. .. versionadded:: 7.2.3 Added the ``min_value`` parameter. c V^8dQhRRRR/#)r#r$r!r%r|r&)r's"r(r))single_int_property..__annotate__sCC9CCr*c<\VPSS44# \dp\S R24ThRp?ii;i)rcz must be an intN)r|r- ValueErrorr)r$er{rzs& r(rg!single_int_property..fgetsE Ctxxg./ / C!TF/":; B Cs =8=c V^8dQhRRRR/#)r#r$r!r?r}r&)r's"r(r)rs " "9 "Z "r*c<Ve\\V\4'd\V\4'd\S RV: 24hSeVS8d\ S RS RV 24hS!V4VeVP SV4R#R#)rlNz must be an int, got z must be >= z, got )r.r|bool TypeErrorrr=)r$r?rnrxrzs&&r(ro!single_int_property..fsets  eS))Zt-D-D4&(=eY GHH$):%l9+VE7&STT T   HHT5 ! r*cV^8dQhRR/#rrr&)r's"r(r)r9r*c,<VPSR4R#rtrCr$rzs&r(rn!single_int_property..fdel tr*rv)rzr{r]rxrgrornsff&d @r(single_int_propertyrs4CC " " Dc **r*c$V^8dQhRRRRRR/#r#namerZdocsr%r^r&)r's"r(r)r)s!+0+0c+0+0+0r*ctaaRS R2V,pRV3RllpRVV3RllpRV3Rllo\W#SVR 7#) zCreate a property to access a value of datetime in UTC timezone. Parameters: name: name of the property docs: documentation string The zV property with all values converted to a :class:`~datetime.datetime` in UTC. c V^8dQhRRRR/#)r#r$r!r%datetime | Noner&)r's"r(r))single_utc_property..__annotate__s ' '9 ' 'r*c8<SV9dR#VPS4p\V\\34'd\P !V4pM \ VRV4pVe\V\4'g\S RV 24h\P!V4#)Get the value.Nr1z must be a datetime in UTC, not ) r-r.rrr from_icalgetattrrrr localize_utc)r$r1r?rs& r(rg!single_utc_property..fgets t  XXd^ b5(+ , ,''+EBb)E = 5$ 7 7!TF*J5'"RS S&&r*c V^8dQhRRRR/#)r#r$r!r?rr&)r's"r(r)rs0090_0r*c<Vf S!V4R#\V\4'g\S RV 24hS!V4VPS\P !V44R#)z Set the valueNz takes a datetime in UTC, not )r.rrr=rrr$r?rnrs&&r(ro!single_utc_property..fsetsV = J %&&tf$B5'JK K T  s''./r*cV^8dQhRR/#rrr&)r's"r(r)rrr*c,<VPSR4R#rtrCr$rs&r(rn!single_utc_property..fdelrr*r]rvrrrgrornsf& @r(single_utc_propertyrsT       ' '00 D$ //r*c ,V^8dQhRRRRRRRRRR/#) r#rrZr other_namezstr | list[str] | Noner{r%r^r&)r's"r(r)r)s4)0)0 )0)0&<)0NQ)0 )0r*caaaaVf.M#\V\4'dV.M \V4oRVVV3RllpRVV3RllpRVV3Rllo\WESVR7#)z2Create a property to access a single string value.c V^8dQhRRRR/#)r#r$r!r%rZr&)r's"r(r),single_string_property..__annotate__s  9  r*c<VPSR4pVf"SFpVPVR4pVfKM VeV.8XdS#\V\4'd V^,#V#)rNrU)r$r4aliasr{r other_namess& r(rg$single_string_property..fgetsi$% >$%.%% >Vr\N fd # #!9  r*c V^8dQhRRRR/#rjr&)r's"r(r)rs""9"Z"r*cH<S!V4VeVPSV4R#R#)z:Set the value. Setting the value to None will delete it. Nrmrs&&r(ro$single_string_property..fsets% T   HHT5 ! r*cV^8dQhRR/#rrr&)r's"r(r)rs""9"r*cb<VPSR4SFpVPVR4K R#rtrC)r$rrrs& r(rn$single_string_property..fdels) t E HHUD !!r*r)r.rZr/r^)rrrr{rgrornrsf&&f @@r(single_string_propertyrsb    j# & &\ *    """" D$ //r*COLORaVThis property specifies a color used for displaying the component. This implements :rfc:`7986` ``COLOR`` property. Property Parameters: IANA and non-standard property parameters can be specified on this property. Conformance: This property can be specified once in an iCalendar object or in ``VEVENT``, ``VTODO``, or ``VJOURNAL`` calendar components. Description: This property specifies a color that clients MAY use when presenting the relevant data to a user. Typically, this would appear as the "background" color of events or tasks. The value is a case-insensitive color name taken from the CSS3 set of names, defined in Section 4.3 of `W3C.REC-css3-color-20110607 `_. Example: ``"turquoise"``, ``"#ffffff"`` .. code-block:: pycon >>> from icalendar import Todo >>> todo = Todo() >>> todo.color = "green" >>> print(todo.to_ical()) BEGIN:VTODO COLOR:green END:VTODO SEQUENCEaThis property defines the revision sequence number of the calendar component within a sequence of revisions. Value Type: INTEGER Property Parameters: IANA and non-standard property parameters can be specified on this property. Conformance: The property can be specified in "VEVENT", "VTODO", or "VJOURNAL" calendar component. Description: When a calendar component is created, its sequence number is 0. It is monotonically incremented by the "Organizer's" CUA each time the "Organizer" makes a significant revision to the calendar component. The "Organizer" includes this property in an iCalendar object that it sends to an "Attendee" to specify the current version of the calendar component. The "Attendee" includes this property in an iCalendar object that it sends to the "Organizer" to specify the version of the calendar component to which the "Attendee" is referring. A change to the sequence number is not the mechanism that an "Organizer" uses to request a response from the "Attendees". The "RSVP" parameter on the "ATTENDEE" property is used by the "Organizer" to indicate that a response from the "Attendees" is requested. Recurrence instances of a recurring component MAY have different sequence numbers. Examples: The following is an example of this property for a calendar component that was just created by the "Organizer": .. code-block:: pycon >>> from icalendar import Event >>> event = Event() >>> event.sequence 0 The following is an example of this property for a calendar component that has been revised 10 different times by the "Organizer": .. code-block:: pycon >>> from icalendar import Calendar >>> calendar = Calendar.example("issue_156_RDATE_with_PERIOD_TZID_khal") >>> event = calendar.events[0] >>> event.sequence 10 Raises: TypeError: If the value is not an ``int``. Booleans are rejected, too, even though ``bool`` subclasses ``int``. ~icalendar.error.InvalidCalendar: If the value is negative. .. versionchanged:: 7.2.3 Negative values are no longer accepted. rxc V^8dQhRRRR/#)r# componentr!r% list[str]r&)r's"r(r)r)s  y Y r*c 2VPR4p\V\4'dE\V\\P P RV4444\V4#Vf\.4pVPRV4VP#)zGet all the categories. CATEGORIESc38"TFqPxK R#5iN)cats).0cats& r( "_get_categories..s.N:Cxx:) r-r.r/_set_categories itertoolschain from_iterable_get_categoriesrr=r)r categoriess& r(rrsy5>]]<5PJ*d##  ...N:.NN O y))r]  lJ/ ??r*c$V^8dQhRRRRRR/#)r#rr!rzSequence[str] | Noner%r:r&)r's"r(r)r)s"  y 0D  r*cV'gV.8wd\V4R#\V4;VR&p\V\4'd4VP 4VP VP 4WnR#R#)zSet the categories.Nr)_del_categoriesrr.r/clearextendr)rrrs&& r(rrsY DBJ "+4T?:Ilj$  JOO$r*c V^8dQhRRRR/#)r#rr!r%r:r&)r's"r(r)r)s&&y&T&r*c*VPRR4R#)zDelete the categories.rNrCrs&r(rrs MM,%r*aThis property defines the categories for a component. The categories property is used to specify categories or subtypes of the calendar component. The categories are useful to search for a calendar component of a particular type and category. Within the calendar components, specify categories as a list of strings. You can get, set, and delete categories for a component. This property can be used in icalendar through its Python attributes of: - :attr:`Available.categories ` - :attr:`Availability.categories ` - :attr:`Calendar.categories ` - :attr:`Event.categories ` - :attr:`Journal.categories ` - :attr:`Todo.categories ` The categories property for ``Available`` and ``Availability`` complies with :rfc:`7953#section-3.1`, for ``Event``, ``Journal``, and ``Todo`` with :rfc:`5545#section-3.8.1.2`, and for ``Calendar`` with :rfc:`7986#section-5.6`. Note: At present, icalendar doesn't take the LANGUAGE parameter as defined in :rfc:`5545#section-3.2.10` into account. Parameters: categories(list[str]): A list of categories as strings. Example: Create an event, add categories to it, print its ical representation, append another category, and finally compare the result against its expected value. .. code-block:: pycon >>> from icalendar import Event >>> event = Event() >>> event.categories = ["Work", "Meeting"] >>> print(event.to_ical()) BEGIN:VEVENT CATEGORIES:Work,Meeting END:VEVENT >>> event.categories.append("Lecture") >>> event.categories == ["Work", "Meeting", "Lecture"] True See also: :attr:`Component.concepts ` c V^8dQhRRRR/#)r#r$r!r%zlist[vCalAddress]r&)r's"r(r)r)s   '8 r*crVPR4pVf .pWR&V#\V\4'dV.#V#)zGet attendees.ATTENDEE)r-r.rr>s& r(_get_attendeesrs@ HHZ E } Z %%%w Lr*c V^8dQhRRRR/#)r#r$r!r?z&list[vCalAddress] | vCalAddress | Noner&)r's"r(r)r)s+Qr*cb\V4VfR#\V\4'gV.pWR&R#)zSet attendees.Nr)_del_attendeesr.r/r>s&&r(_set_attendeesrs.4 } eT " "r*cV^8dQhRR/#rrr&)r's"r(r)r)sr*c*VPRR4R#)zDelete all attendees.rNrCrEs&r(rrsHHZr*abATTENDEE defines one or more "Attendees" within a calendar component. Conformance: This property MUST be specified in an iCalendar object that specifies a group-scheduled calendar entity. This property MUST NOT be specified in an iCalendar object when publishing the calendar information (e.g., NOT in an iCalendar object that specifies the publication of a calendar user's busy time, event, to-do, or journal). This property is not specified in an iCalendar object that specifies only a time zone definition or that defines calendar components that are not group-scheduled components, but are components only on a single user's calendar. Description: This property MUST only be specified within calendar components to specify participants, non-participants, and the chair of a group-scheduled calendar entity. The property is specified within an "EMAIL" category of the "VALARM" calendar component to specify an email address that is to receive the email type of iCalendar alarm. Examples: Add a new attendee to an existing event. .. code-block:: pycon >>> from icalendar import Event, vCalAddress >>> event = Event() >>> event.attendees.append(vCalAddress("mailto:me@my-domain.com")) >>> print(event.to_ical()) BEGIN:VEVENT ATTENDEE:mailto:me@my-domain.com END:VEVENT Create an email alarm with several attendees: >>> from icalendar import Alarm, vCalAddress >>> alarm = Alarm.new(attendees = [ ... vCalAddress("mailto:me@my-domain.com"), ... vCalAddress("mailto:you@my-domain.com"), ... ], summary = "Email alarm") >>> print(alarm.to_ical()) BEGIN:VALARM ATTENDEE:mailto:me@my-domain.com ATTENDEE:mailto:you@my-domain.com SUMMARY:Email alarm END:VALARM UIDa UID specifies the persistent, globally unique identifier for a component. We recommend using :func:`uuid.uuid4` to generate new values. Returns: The value of the UID property as a string or ``""`` if no value is set. Description: The "UID" itself MUST be a globally unique identifier. The generator of the identifier MUST guarantee that the identifier is unique. This is the method for correlating scheduling messages with the referenced "VEVENT", "VTODO", or "VJOURNAL" calendar component. The full range of calendar components specified by a recurrence set is referenced by referring to just the "UID" property value corresponding to the calendar component. The "RECURRENCE-ID" property allows the reference to an individual instance within the recurrence set. This property is an important method for group-scheduling applications to match requests with later replies, modifications, or deletion requests. Calendaring and scheduling applications MUST generate this property in "VEVENT", "VTODO", and "VJOURNAL" calendar components to assure interoperability with other group- scheduling applications. This identifier is created by the calendar system that generates an iCalendar object. Implementations MUST be able to receive and persist values of at least 255 octets for this property, but they MUST NOT truncate values in the middle of a UTF-8 multi-octet sequence. :rfc:`7986` states that UID can be used, for example, to identify duplicate calendar streams that a client may have been given access to. It can be used in conjunction with the "LAST-MODIFIED" property also specified on the "VCALENDAR" object to identify the most recent version of a calendar. Conformance: :rfc:`5545` states that the "UID" property can be specified on "VEVENT", "VTODO", and "VJOURNAL" calendar components. :rfc:`7986` modifies the definition of the "UID" property to allow it to be defined in an iCalendar object. :rfc:`9074` adds a "UID" property to "VALARM" components to allow a unique identifier to be specified. The value of this property can then be used to refer uniquely to the "VALARM" component. This property can be specified once only. Security: :rfc:`7986` states that UID values MUST NOT include any data that might identify a user, host, domain, or any other security- or privacy-sensitive information. It is RECOMMENDED that calendar user agents now generate "UID" values that are hex-encoded random Universally Unique Identifier (UUID) values as defined in Sections 4.4 and 4.5 of :rfc:`4122`. You can use the :mod:`uuid` module to generate new UUIDs. Compatibility: For Alarms, ``X-ALARMUID`` is also considered. Examples: The following is an example of such a property value: ``5FC53010-1267-4F8E-BC28-1D7AE55A7C99``. Set the UID of a calendar: .. code-block:: pycon >>> from icalendar import Calendar >>> from uuid import uuid4 >>> calendar = Calendar() >>> calendar.uid = uuid4() >>> print(calendar.to_ical()) BEGIN:VCALENDAR UID:d755cef5-2311-46ed-a0e1-6733c9e15c63 END:VCALENDAR SUMMARYaSUMMARY defines a short summary or subject for the calendar component. Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. Conformance: The property can be specified in "VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar components. Description: This property is used in the "VEVENT", "VTODO", and "VJOURNAL" calendar components to capture a short, one-line summary about the activity or journal entry. This property is used in the "VALARM" calendar component to capture the subject of an EMAIL category of alarm. Examples: The following is an example of this property: .. code-block:: pycon SUMMARY:Department Party DESCRIPTIONaDESCRIPTION provides a more complete description of the calendar component than that provided by the "SUMMARY" property. Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. Conformance: The property can be specified in the "VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar components. The property can be specified multiple times only within a "VJOURNAL" calendar component. Description: This property is used in the "VEVENT" and "VTODO" to capture lengthy textual descriptions associated with the activity. This property is used in the "VALARM" calendar component to capture the display text for a DISPLAY category of alarm, and to capture the body text for an EMAIL category of alarm. Examples: The following is an example of this property with formatted line breaks in the property value: .. code-block:: pycon DESCRIPTION:Meeting to provide technical review for "Phoenix" design.\nHappy Face Conference Room. Phoenix design team MUST attend this meeting.\nRSVP to team leader. c4V^8dQhRRRRRRRRR RR RR R /#) r#rzrZ value_attrr\ value_typez tuple[type]type_deftyper]vPropconvertz!Callable[[object], object] | Noner&)r's"r(r)r)sWC0C0 C0C0C0 C0 C0  C0/C0r*caaaaaa RVVVV3RllpRVV VVV3RllpVR,;VPR&VPR&RV3R llo R S R V R 2p \WxS V 4#) aUCreate a single property getter and setter. Parameters: prop: The name of the property. value_attr: The name of the attribute to get the value from. value_type: The type of the value. type_def: The type of the property. doc: The docstring of the property. vProp: The type of the property from :mod:`icalendar.prop`. cV^8dQhRR/#rrr&)r's"r(r),create_single_property..__annotate__sIr*cR<\4pVPSV4pW!JdR#\V\4'd\ RS R24hSfTM \ VSV4pSfTMS!V4p\VS4'g+\ S RRP RS44 RV R24hV#)Nz Multiple z defined.z must be either a  or c38"TFqPxK R#5ir__name__rts& r(r8create_single_property..p_get..s>:azz:r, not .)objectr-r.r/rrjoin)r$r{r4r?rrzrrs& r(p_get%create_single_property..p_gets($(   fd # #!IdV9"=> >$,'&*f2U gen%,,!&*;;>:>>?@wa!   r*c V^8dQhRRRR/#r9r&)r's"r(r)rs//I//r*cr<Vf S!V4R#Se S!V4MTp\VS4'g<\RRPRS44 R\V4P R24hS!V4VS&SVP 9d1VP FpVS8wgK VP VR4K R#R#)NzUse rc38"TFqPxK R#5irrrs& r(r8create_single_property..p_set..s"Bz!::zrrr)r.rrrr exclusiverD)r$r? other_proprp_delrzrrs&& r(p_set%create_single_property..p_sets = $K ")"55%,,v{{"Bz"BBCDE{++,A/ 5\T 4>> !"nn %HHZ.- "r*Nr?r%cV^8dQhRR/#rrr&)r's"r(r)rsIr*c*<VPS4R#rrCrs&r(r%create_single_property..p_dels r*rz property. z To delete the value, either use ``del`` or set it to ``None``. Raises: InvalidCalendar: if the attribute has invalid values. )__annotations__r^) rzrrrr]rrrrp_docrs fff&&ff @r(create_single_propertyr sz("// HPRVVE'"U%:%:8%DTFE  E E% //r*zX-MOZ-SNOOZE-TIMEz1Thunderbird: Alarms before this time are snoozed.z X-MOZ-LASTACKz6Thunderbird: Alarms before this time are acknowledged.c V^8dQhRRRR/#)r#r$r!r%timedelta | Noner&)r's"r(r)r)s   .> r*c\4pVPRV4pW!JdR#\VRR4pVf#\R\ V4P R24hV#)zGetter for property DURATION.durationNtdz"DURATION must be a timedelta, not r)rr-rrrr)r$r{rr4s& r(property_get_durationrs`hGxx G,H XtT *F ~0h1H1H0I K   Mr*c V^8dQhRRRR/#)r#r$r!r?rr&)r's"r(r)r)$s   2B r*cVfVPRR4R#\V\4'g#\R\ V4P R24h\ V4VR&VPR4VPR4R#)zSetter for property DURATION.NrUse timedelta, not rDTENDDUE)rDr.rrrrrr>s&&r(property_set_durationr$sk } T" eY ' '-d5k.B.B-C1EFF 'DHHWHHUOr*cV^8dQhRR/#rrr&)r's"r(r)r)0s r*c(VPR4R#)zDelete property DURATION.DURATIONNrCrEs&r(property_del_durationr0sHHZr*aThe DURATION property. The "DTSTART" property for a "{component}" specifies the inclusive start of the {component}. The "DURATION" property in conjunction with the DTSTART property for a "{component}" calendar component specifies the non-inclusive end of the event. If you would like to calculate the duration of a {component}, do not use this. Instead use the duration property (lower case). c V^8dQhRRRR/#)r#rrZr%r^r&)r's"r(r)r)Bsr*c ^\\\\\P VR74#)zReturn the duration property.r)r^rrrproperty_doc_duration_templater'rs&r(duration_propertyr!Bs) &-- -B  r*c$V^8dQhRRRRRR/#rr&)r's"r(r)r)Ls!,,c,,,r*cXaaRV3RllpRVV3RllpRV3Rllo\W#SV4#)ziGet a property that can occur several times and is text. Examples: Journal.descriptions, Event.comments c V^8dQhRRRR/#r#r$r!r%rr&)r's"r(r))multi_text_property..__annotate__Rs9r*ch<VPS4pVf.#\V\4'gV.#V#)zGet the values.)r-r.r)r$ descriptionsrs& r(rg!multi_text_property..fgetRs6xx~  I,77 > !r*c V^8dQhRRRR/#)r#r$r!valueszstr | Sequence[str] | Noner&)r's"r(r)r&[s , ,9 ,&@ ,r*c<S!V4VfR#\V\4'dVPSV4R#VFpVPSV4K R#)zSet the values.N)r.rZr=)r$r+ descriptionrnrs&& r(ro!multi_text_property..fset[sE T >  fc " " HHT6 "% {+ &r*cV^8dQhRR/#rrr&)r's"r(r)r&fs9r*c*<VPS4R#)zDelete the values.NrCrs&r(rn!multi_text_property..fdelfs r*rvrsf& @r(multi_text_propertyr2Ls2  , , Dd ++r*aSDESCRIPTION provides a more complete description of the calendar component than that provided by the "SUMMARY" property. Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. Conformance: The property can be specified multiple times only within a "VJOURNAL" calendar component. Description: This property is used in the "VJOURNAL" calendar component to capture one or more textual journal entries. Examples: The following is an example of this property with formatted line breaks in the property value: .. code-block:: pycon DESCRIPTION:Meeting to provide technical review for "Phoenix" design.\nHappy Face Conference Room. Phoenix design team MUST attend this meeting.\nRSVP to team leader. COMMENTaCOMMENT is used to specify a comment to the calendar user. Purpose: This property specifies non-processing information intended to provide a comment to the calendar user. Conformance: In :rfc:`5545`, this property can be specified multiple times in "VEVENT", "VTODO", "VJOURNAL", and "VFREEBUSY" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components. In :rfc:`7953`, this property can be specified multiple times in "VAVAILABILITY" and "VAVAILABLE". Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. z RECURRENCE-IDr1aU Identify a specific occurrence of a recurring calendar object. This property is used together with ``UID`` and ``SEQUENCE`` to refer to one particular instance in a recurrence set. The value is the original start date or datetime of that instance, not the rescheduled time. The value is usually a DATE-TIME and must use the same value type as the ``DTSTART`` property in the same component. A DATE value may be used for all-day items instead. This property corresponds to ``RECURRENCE-ID`` as defined in RFC 5545 and may appear in recurring ``VEVENT``, ``VTODO``, and ``VJOURNAL`` components. c V^8dQhRRRR/#)r#r$r!r%zvCalAddress | Noner&)r's"r(r)r)s$!$!$!'9$!r*c$VPR4#)aORGANIZER defines the organizer for a calendar component. Property Parameters: IANA, non-standard, language, common name, directory entry reference, and sent-by property parameters can be specified on this property. Conformance: This property MUST be specified in an iCalendar object that specifies a group-scheduled calendar entity. This property MUST be specified in an iCalendar object that specifies the publication of a calendar user's busy time. This property MUST NOT be specified in an iCalendar object that specifies only a time zone definition or that defines calendar components that are not group-scheduled components, but are components only on a single user's calendar. Description: This property is specified within the "VEVENT", "VTODO", and "VJOURNAL" calendar components to specify the organizer of a group-scheduled calendar entity. The property is specified within the "VFREEBUSY" calendar component to specify the calendar user requesting the free or busy time. When publishing a "VFREEBUSY" calendar component, the property is used to specify the calendar that the published busy time came from. The property has the property parameters "CN", for specifying the common or display name associated with the "Organizer", "DIR", for specifying a pointer to the directory information associated with the "Organizer", "SENT-BY", for specifying another calendar user that is acting on behalf of the "Organizer". The non-standard parameters may also be specified on this property. If the "LANGUAGE" property parameter is specified, the identified language applies to the "CN" parameter value. ORGANIZER)r-rEs&r(_get_organizerr7sH 88K  r*c V^8dQhRRRR/#)r#r$r!r?zvCalAddress | str | Noner&)r's"r(r)r)s%%%+C%r*cL\V4VeVPRV4R#R#)Set the value.Nr6)_del_organizerr=r>s&&r(_set_organizerr<s#4  e$r*cV^8dQhRR/#rrr&)r's"r(r)r)sr*c(VPR4R#)zDelete the value.r6NrCrEs&r(r;r;sHH[r*c ,V^8dQhRRRRRRRRRR /#) r#rrZenumz type[StrEnum]r{r rr%r^r&)r's"r(r)r)s455 5"5-45.__annotate__s  9  r*cZ<SPV4pVS8XdS#S!\V44#)r)rgrZ)r$r?r{r@rzs& r(rg)single_string_enum_property..fgets, $ G NCJr*c$V^8dQhRRRRRR/#)r#r$r!r?zstr | StrEnum | Noner%r:r&)r's"r(r)rCs"9%9dr*c<<VR8XdRpSPW4R#)r:rN)ro)r$r?rzs&&r(ro)single_string_enum_property..fsets B;E $r*r)rr^rn)rr@r{rrgrorzs&ff& @r(single_string_enum_propertyrIs: "$g >D   D t 44r*r aBUSYTYPE specifies the default busy time type. Returns: :class:`icalendar.enums.BUSYTYPE` Description: This property is used to specify the default busy time type. The values correspond to those used by the "FBTYPE" parameter used on a "FREEBUSY" property, with the exception that the "FREE" value is not used in this property. If not specified on a component that allows this property, the default is "BUSY- UNAVAILABLE". cV^8dQhRR/#)r#r%r^r&)r's"r(r)r)sAAxAr*caa^RIHo\R^R^R7oVV3Rlp\VSPSP SP 4#)) _clamp_repeatREPEATaGThe number of additional times the alarm is triggered after the initial trigger. Defaults to ``0``, meaning the alarm fires once. Must be paired with :attr:`~icalendar.cal.alarm.Alarm.DURATION`. Conforms with :rfc:`5545#section-3.8.6.2`. The value is capped at :data:`icalendar.config.MAX_ALARM_REPEAT` on read. Raises: TypeError: If the value is not an ``int``. Booleans are rejected, too, even though ``bool`` subclasses ``int``. ~icalendar.error.InvalidCalendar: If the value is negative. .. versionchanged:: 7.2.3 Negative values are no longer accepted. rc2<S!SPV44#r)rg)r$_baserMs&r(rg#_make_repeat_property..fget2sUZZ-..r*)icalendar.configrMrr^rorn__doc__)rgrPrMs @@r(_make_repeat_propertyrTsD.    ' E,/ D%**ejj%-- @@r*PRIORITYa- Conformance: This property can be specified in "VEVENT" and "VTODO" calendar components according to :rfc:`5545`. :rfc:`7953` adds this property to "VAVAILABILITY". Description: This priority is specified as an integer in the range 0 to 9. A value of 0 specifies an undefined priority. A value of 1 is the highest priority. A value of 2 is the second highest priority. Subsequent numbers specify a decreasing ordinal priority. A value of 9 is the lowest priority. A CUA with a three-level priority scheme of "HIGH", "MEDIUM", and "LOW" is mapped into this property such that a property value in the range of 1 to 4 specifies "HIGH" priority. A value of 5 is the normal or "MEDIUM" priority. A value in the range of 6 to 9 is "LOW" priority. A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ..., "C3" is mapped into this property such that a property value of 1 specifies "A1", a property value of 2 specifies "A2", a property value of 3 specifies "A3", and so forth up to a property value of 9 specifies "C3". Other integer values are reserved for future use. Within a "VEVENT" calendar component, this property specifies a priority for the event. This property may be useful when more than one event is scheduled for a given time period. Within a "VTODO" calendar component, this property specified a priority for the to-do. This property is useful in prioritizing multiple action items for a given time period. Raises: TypeError: If the value is not an ``int``. Booleans are rejected, too, even though ``bool`` subclasses ``int``. ~icalendar.error.InvalidCalendar: If the value is negative. .. versionchanged:: 7.2.3 Negative values are no longer accepted. r a CLASS specifies the class of the calendar component. Returns: :class:`icalendar.enums.CLASS` Description: An access classification is only one component of the general security system within a calendar application. It provides a method of capturing the scope of the access the calendar owner intends for information within an individual calendar entry. The access classification of an individual iCalendar component is useful when measured along with the other security components of a calendar system (e.g., calendar user authentication, authorization, access rights, access role, etc.). Hence, the semantics of the individual access classifications cannot be completely defined by this memo alone. Additionally, due to the "blind" nature of most exchange processes using this memo, these access classifications cannot serve as an enforcement statement for a system receiving an iCalendar object. Rather, they provide a method for capturing the intention of the calendar owner for the access to the calendar component. If not specified in a component that allows this property, the default value is PUBLIC. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the PRIVATE value. r arTRANSP defines whether or not an event is transparent to busy time searches. Returns: :class:`icalendar.enums.TRANSP` Description: Time Transparency is the characteristic of an event that determines whether it appears to consume time on a calendar. Events that consume actual time for the individual or resource associated with the calendar SHOULD be recorded as OPAQUE, allowing them to be detected by free/busy time searches. Other events, which do not take up the individual's (or resource's) time SHOULD be recorded as TRANSPARENT, making them invisible to free/ busy time searches. r aSTATUS defines the overall status or confirmation for the calendar component. Returns: :class:`icalendar.enums.STATUS` The default value is ``""``. Description: In a group-scheduled calendar component, the property is used by the "Organizer" to provide a confirmation of the event to the "Attendees". For example in a "VEVENT" calendar component, the "Organizer" can indicate that a meeting is tentative, confirmed, or cancelled. In a "VTODO" calendar component, the "Organizer" can indicate that an action item needs action, is completed, is in process or being worked on, or has been cancelled. In a "VJOURNAL" calendar component, the "Organizer" can indicate that a journal entry is draft, final, or has been cancelled or removed. URLa. A Uniform Resource Locator (URL) associated with a calendar component. This property specifies a URI where a more dynamic rendition of the calendar information can be found. It is commonly used to reference related resources or provide additional information about the component. According to :rfc:`5545#section-3.8.4.6`, this property can be specified once in "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar components. Since :rfc:`7986#section-5.5`, this property can also be defined on a "VCALENDAR". :rfc:`7953#section-3.1` allows this property in "VAVAILABILITY" components. This property may be used in a calendar component to convey a location where a more dynamic rendition of the calendar information can be found. If both the URL property and Content-Location MIME header are specified, they MUST point to the same resource. This differs from the SOURCE property, which identifies where calendar data can be refreshed from, whereas URL provides an alternative representation of the current calendar data. Examples: Set a URL for an event that references additional information: .. code-block:: pycon >>> from icalendar import Event >>> event = Event() >>> event.add('url', 'http://example.com/events/meeting-2025') >>> print(event.to_ical().decode('utf-8')) BEGIN:VEVENT URL:http://example.com/events/meeting-2025 END:VEVENT Set a URL for a calendar: .. code-block:: pycon >>> from icalendar import Calendar >>> calendar = Calendar() >>> calendar.add('url', 'http://example.com/pub/calendars/jsmith/mytime.ics') >>> print(calendar.to_ical().decode('utf-8')) BEGIN:VCALENDAR URL:http://example.com/pub/calendars/jsmith/mytime.ics END:VCALENDAR See also: :attr:`~icalendar.cal.calendar.Calendar.source` for specifying from where calendar data can be refreshed. icalendar implementations: - :attr:`Availability.url ` - :attr:`Calendar.url ` - :attr:`Event.url ` - :attr:`FreeBusy.url ` - :attr:`Journal.url ` - :attr:`Todo.url ` SOURCEaA URI from where calendar data can be refreshed. Description: This property identifies a location where a client can retrieve updated data for the calendar. Clients SHOULD honor any specified "REFRESH-INTERVAL" value when periodically retrieving data. Note that this property differs from the "URL" property in that "URL" is meant to provide an alternative representation of the calendar data rather than the original location of the data. Conformance: This property can be specified once in an iCalendar object. Example: The following is an example of this property: .. code-block:: ics SOURCE;VALUE=URI:https://example.com/holidays.ics LOCATIONaThe intended venue for the activity defined by a calendar component. Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. Conformance: Since :rfc:`5545`, this property can be specified in "VEVENT" or "VTODO" calendar component. :rfc:`7953` adds this property to "VAVAILABILITY" and "VAVAILABLE". Description: Specific venues such as conference or meeting rooms may be explicitly specified using this property. An alternate representation may be specified that is a URI that points to directory information with more structured specification of the location. For example, the alternate representation may specify either an LDAP URL :rfc:`4516` pointing to an LDAP server entry or a CID URL :rfc:`2392` pointing to a MIME body part containing a Virtual-Information Card (vCard) :rfc:`2426` for the location. CONTACTaaContact information associated with the calendar component. Purpose: This property is used to represent contact information or alternately a reference to contact information associated with the calendar component. Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. Conformance: In :rfc:`5545`, this property can be specified in a "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar component. In :rfc:`7953`, this property can be specified in a "VAVAILABILITY" amd "VAVAILABLE" calendar component. Description: The property value consists of textual contact information. An alternative representation for the property value can also be specified that refers to a URI pointing to an alternate form, such as a vCard :rfc:`2426`, for the contact information. Example: The following is an example of this property referencing textual contact information: .. code-block:: ics CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234 The following is an example of this property with an alternate representation of an LDAP URI to a directory entry containing the contact information: .. code-block:: ics CONTACT;ALTREP="ldap://example.com:6666/o=ABC%20Industries\, c=US???(cn=Jim%20Dolittle)":Jim Dolittle\, ABC Industries\, +1-919-555-1234 The following is an example of this property with an alternate representation of a MIME body part containing the contact information, such as a vCard :rfc:`2426` embedded in a text/ directory media type :rfc:`2425`: .. code-block:: ics CONTACT;ALTREP="CID:part3.msg970930T083000SILVER@example.com": Jim Dolittle\, ABC Industries\, +1-919-555-1234 The following is an example of this property referencing a network resource, such as a vCard :rfc:`2426` object containing the contact information: .. code-block:: ics CONTACT;ALTREP="http://example.com/pdi/jdoe.vcf":Jim Dolittle\, ABC Industries\, +1-919-555-1234 c V^8dQhRRRR/#)r#rrZrr&)r's"r(r)r)rs++c++r*c\W4#)z>Create a property to access the values with a proper timezone.)r)rrs&&r(_timezone_datetime_propertyr\rs t **r*DTSTARTaStart of the component. This is almost the same as :attr:`Event.DTSTART ` with one exception: The values MUST have a timezone and DATE is not allowed. Description: :rfc:`7953`: If specified, the "DTSTART" and "DTEND" properties in "VAVAILABILITY" components and "AVAILABLE" subcomponents MUST be "DATE-TIME" values specified as either the date with UTC time or the date with local time and a time zone reference. raStart of the component. This is almost the same as :attr:`Event.DTEND ` with one exception: The values MUST have a timezone and DATE is not allowed. Description: :rfc:`7953`: If specified, the "DTSTART" and "DTEND" properties in "VAVAILABILITY" components and "AVAILABLE" subcomponents MUST be "DATE-TIME" values specified as either the date with UTC time or the date with local time and a time zone reference. cV^8dQhRR/#r#r%rr&)r's"r(r)r)s(8r*cVPpV'dV#VPpVfR#VPpVf \R4hW#, #)?Compute the duration of this component. If there is no :attr:`DTEND` or :attr:`DURATION` set, this is None. Otherwise, the duration is calculated from :attr:`DTSTART` and :attr:`DTEND`/:attr:`DURATION`. This is in accordance with :rfc:`7953`: If "DTEND" or "DURATION" are not present, then the end time is unbounded. Nz&Cannot compute duration without start.)rrr]r)r$rendstarts& r(rfc_7953_duration_propertyrdsH}}H **C { LLE }!"JKK ;r*cV^8dQhRR/#r_r&)r's"r(r)r)s#3r*cVPpV'd$VPpVf \R4hW!,#VPpVfR#V#)raNz!Cannot compute end without start.)rr]rr)r$rrcrbs& r(rfc_7953_end_propertyrgsI}}H  =%&IJ J **C { Jr*cV^8dQhRR/#)r#r?rr&)r's"r(r)r)sxr*cWnR#rrr>s&&r(rgrgsJr*c V=R#rrjrEs&r(rgrgs r*c ,V^8dQhRRRRRRRRRR/#) r#rr!start_propertyrZ end_propertycomponent_namer%zGtuple[date | datetime | None, date | datetime | None, timedelta | None]r&)r's"r(r)r)s;: : : : :  : M : r*c\WR4p\WR4pVPpVe$Ve VR8XdRMRpRV RV R2p\V4hVe4\V4'd#VeVP^8wdRp\V4hVe:Ve6\V4\V48wdVR8XdRMRpRV R 2p\V4hWEV3#) a Validate the component and return start, end, and duration. This tests validity according to :rfc:`5545` rules for ``Event`` and ``Todo`` components. Parameters: component: The component to validate, either ``Event`` or ``Todo``. start_property: The start property name, ``DTSTART``. end_property: The end property name, either ``DTEND`` for ``Event`` or ``DUE`` for ``Todo``. component_name: The component name for error messages, either ``VEVENT`` or ``VTODO``. Returns: tuple: (start, end, duration) values from the component. Raises: ~error.InvalidCalendar: If the component violates RFC 5545 constraints. Nrrz Only one of z and DURATION may be in a z , not both.:When DTSTART is a date, DURATION must be of days or weeks.z DTSTART and z3 must be of the same type, either date or datetime.)rrrrseconds) rrmrnrorcrbrend_namemsgs &&&& r(&get_start_end_duration_with_validationrus6 It 4E )4 0C!!H*g5758*%)*+ 7 c""  ENN     !Jc"" S_73<1O*g5758*$W X c"" x r*c V^8dQhRRRR/#)r#rr!r%date | datetimer&)r's"r(r)r)s)r*cNVP4wrpVfRp\V4hV#)z Get the start property with validation. Parameters: component: The component from which to get its start property. Returns: The ``DTSTART`` value. Raises: ~error.IncompleteComponent: If no ``DTSTART`` is present. zNo DTSTART given.)_get_start_end_durationr)rrc_end _durationrts& r(get_start_propertyr|s1'>>@E }!!#&& Lr*c$V^8dQhRRRRRR/#)r#rr!rnrZr%rwr&)r's"r(r)r)%s!** ***r*c~VP4wr#pVfRVfNVfVR8XdRMRpRV R2p\V4hVR8Xd%\V4'dV\^R7,#V#VeQVe1VPR8XdVP 4^8:dV#W$,#VR8XdRMRpRV R2p\V4hV#)a Get the end property with fallback logic for ``Event`` and ``Todo`` components. Parameters: component: The component to get end from end_property: The end property name, either ``DTEND`` for ``Event`` or ``DUE`` for ``Todo``. Returns: The computed end value. Raises: ~error.IncompleteComponent: If the provided information is incomplete to compute the end property. rrzNo z or DURATION+DTSTART given.)daysVEVENT)ryrrrr total_seconds)rrnrcrbrrsrts&& r(get_end_propertyr%s$%<<>E {x' =".'"9wuHz!<=C%c* * 7 "wu~~9!,, ,   ~~)h.D.D.F!.K # #*g575H:89!#&& Jr*c V^8dQhRRRR/#)r#rr!r%rr&)r's"r(r)r)Rs++Y+9+r*cpRV9dVR,P#VPVP, #)z Get the duration property with fallback calculation from start and end. Parameters: component: The component from which to get its duration property. Returns: The duration as a timedelta. r)r1rbrcrs&r(get_duration_propertyrRs2Y$''' ==9?? **r*c ,V^8dQhRRRRRRRRR R /#) r#rr!rrlockedzLiteral['start', 'end']rnrZr%r:r&)r's"r(r)r)es:2222 $2 2  2r*c0VfRV9dR#VPpW@nR#\V\4'g%R\ V4P R2p\ V4hVPpVe0\V4'dVP^8wdRp\V4hVR8Xd,VfRp\V4hVPVR4WnR#VR8Xd4VPpWq, VnVPVR4WnR#R V: 2p\V4h) a Set the duration with explicit locking behavior for ``Event`` and ``Todo``. Parameters: component: The component to modify, either ``Event`` or ``Todo``. duration: The duration to set, or ``None`` to convert to ``DURATION`` property. locked: Which property to keep unchanged, either ``start`` or ``end``. end_property: The end property name, either ``DTEND`` for ``Event`` or ``DUE`` for ``Todo``. Nrrrrqrcz:Cannot set duration without DTSTART. Set start time first.rbz%locked must be 'start' or 'end', not )rrr.rrrrr]rrrrrrDrbr)rrrrncurrent_durationrtrc current_ends&&&& r(set_duration_with_lockingres$  " $--- h * *#DN$;$;#n   E WU^^0@0@A0EJc""  =NC%c* * lD)% 5mm '2  lD)%5fZ@or*c ,V^8dQhRRRRRRRRR R /#) r#rr!rcrwrz!Literal['duration', 'end'] | NonernrZr%r:r&)r's"r(r)r)s:/// / ./ /  /r*cXVfRV9dRpM W09dRpMRpVR8XdBRV9gW09d VPMRpWnVeVPVR4W@nR#R#VR8Xd3VPpWnVPRR4\ WV4R#RV: 2p\ V4h)a Set the start with explicit locking behavior for ``Event`` and ``Todo`` components. Parameters: component: The component to modify, either ``Event`` or ``Todo``. start: The start time to set. locked: Which property to keep unchanged, either ``duration``, ``end``, or ``None`` for auto-detect. end_property: The end property name, either ``DTEND`` for ``Event`` or ``DUE`` for ``Todo``. Nrrrbz/locked must be 'duration', 'end', or None, not )rr]rDrrbsetattrr)rrcrrnrrrts&&&& r(set_start_with_lockingrs$~  "F  &F F Y&,*C     "  ' MM, -!1  ( 5mm ! j$' 5?zJor*c ,V^8dQhRRRRRRRRR R /#) r#rr!rbrwrzLiteral['start', 'duration']rnrZr%r:r&)r's"r(r)r)s:  )   r*cVR8Xd!VPRR4\WV4R#VR8Xd4VPpW, VnVPVR4W@nR#RV: 2p\ V4h)av Set the end with explicit locking behavior for Event and Todo components. Parameters: component: The component to modify, either ``Event`` or ``Todo``. end: The end time to set. locked: Which property to keep unchanged, either ``start`` or ``duration``. end_property: The end property name, either ``DTEND`` for ``Event`` or ``DUE`` for ``Todo``. rcrNrz*locked must be 'start' or 'duration', not )rDrrr]rr)rrbrrnrrts&&&& r(set_end_with_lockingrsm" j$' - : $--2  lD)-:6*Eor*c V^8dQhRRRR/#)r#r$r!r%z list[Image]r&)r's"r(r)r)s>>i>K>r*cVPR.4p\V\4'gV.pVUu.uFp\P!V4NK up#uupi)aIMAGE specifies an image associated with the calendar or a calendar component. Description: This property specifies an image for an iCalendar object or a calendar component via a URI or directly with inline data that can be used by calendar user agents when presenting the calendar data to a user. Multiple properties MAY be used to specify alternative sets of images with, for example, varying media subtypes, resolutions, or sizes. When multiple properties are present, calendar user agents SHOULD display only one of them, picking one that provides the most appropriate image quality, or display none. The "DISPLAY" parameter is used to indicate the intended display mode for the image. The "ALTREP" parameter, defined in :rfc:`5545`, can be used to provide a "clickable" image where the URI in the parameter value can be "launched" by a click on the image in the calendar user agent. Conformance: This property can be specified multiple times in an iCalendar object or in "VEVENT", "VTODO", or "VJOURNAL" calendar components. .. note:: At the present moment, this property is read-only. If you require a setter, please open an issue or a pull request. IMAGE)r-r.rrfrom_property_value)r$imagesimgs& r( _get_imagesrsK8XXgr "F fn - -6< =fsE % %c *f == =Ac V^8dQhRRRR/#)r#r$r!r%zlist[Conference]r&)r's"r(r)r)s#YKYK9YK)9YKr*cVPR.4p\V\4'gV.pVUu.uFp\P!V4NK up#uupi)a- Return the CONFERENCE properties as a list. Purpose: This property specifies information for accessing a conferencing system. Conformance: This property can be specified multiple times in a "VEVENT" or "VTODO" calendar component. Description: This property specifies information for accessing a conferencing system for attendees of a meeting or task. This might be for a telephone-based conference number dial-in with access codes included (such as a tel: URI :rfc:`3966` or a sip: or sips: URI :rfc:`3261`), for a web-based video chat (such as an http: or https: URI :rfc:`7230`), or for an instant messaging group chat room (such as an xmpp: URI :rfc:`5122`). If a specific URI for a conferencing system is not available, a data: URI :rfc:`2397` containing a text description can be used. A conference system can be a bidirectional communication channel or a uni-directional "broadcast feed". The "FEATURE" property parameter is used to describe the key capabilities of the conference system to allow a client to choose the ones that give the required level of interaction from a set of multiple properties. The "LABEL" property parameter is used to convey additional details on the use of the URI. For example, the URIs or access codes for the moderator and attendee of a teleconference system could be different, and the "LABEL" property parameter could be used to "tag" each "CONFERENCE" property to indicate which is which. The "LANGUAGE" property parameter can be used to specify the language used for text values used with this property (as per Section 3.2.10 of :rfc:`5545`). Example: The following are examples of this property: .. code-block:: ics CONFERENCE;VALUE=URI;FEATURE=PHONE,MODERATOR; LABEL=Moderator dial-in:tel:+1-412-555-0123,,,654321 CONFERENCE;VALUE=URI;FEATURE=PHONE; LABEL=Attendee dial-in:tel:+1-412-555-0123,,,555123 CONFERENCE;VALUE=URI;FEATURE=PHONE; LABEL=Attendee dial-in:tel:+1-888-555-0456,,,555123 CONFERENCE;VALUE=URI;FEATURE=CHAT; LABEL=Chat room:xmpp:chat-123@conference.example.com CONFERENCE;VALUE=URI;FEATURE=AUDIO,VIDEO; LABEL=Attendee dial-in:https://chat.example.com/audio?id=123456 Get all conferences: .. code-block:: pycon >>> from icalendar import Event >>> event = Event() >>> event.conferences [] Set a conference: .. code-block:: pycon >>> from icalendar import Event, Conference >>> event = Event() >>> event.conferences = [ ... Conference( ... "tel:+1-412-555-0123,,,654321", ... feature="PHONE,MODERATOR", ... label="Moderator dial-in", ... language="EN", ... ) ... ] >>> print(event.to_ical()) BEGIN:VEVENT CONFERENCE;FEATURE="PHONE,MODERATOR";LABEL=Moderator dial-in;LANGUAGE=EN;V ALUE=URI:tel:+1-412-555-0123,,,654321 END:VEVENT CONFERENCE)r-r.rrfrom_urir$ conferences conferences& r(_get_conferencesrsLl((<,K k> 2 2"m >I Jk J   +k JJ Jrc V^8dQhRRRR/#)r#r$r!rzlist[Conference] | Noner&)r's"r(r)r)ms44943J4r*c\V4T;'g.F#pVPRVP44K% R#)zSet the conferences.rN)_del_conferencesr=to_urirs&& r(_set_conferencesrms6T!''R'  z0023(r*cV^8dQhRR/#rrr&)r's"r(r)r)ts9r*c(VPR4R#)zDelete all conferences.rNrCrEs&r(rrtsHH\r*c V^8dQhRRRR/#)r#r$r!r%z!list[vUri | vUid | vXmlReference]r&)r's"r(r)r)|smmYm#Dmr*c\VPR.4p\V\4'gV.pV#)aLINK properties as a list. Purpose: LINK provides a reference to external information related to a component. Property Parameters: The VALUE parameter is required. Non-standard, link relation type, format type, label, and language parameters can also be specified on this property. The LABEL parameter is defined in :rfc:`7986`. Conformance: This property can be specified zero or more times in any iCalendar component. LINK is specified in :rfc:`9253`. The LINKREL parameter is required. Description: When used in a component, the value of this property points to additional information related to the component. For example, it may reference the originating web server. This property is a serialization of the model in :rfc:`8288`, where the link target is carried in the property value, the link context is the containing calendar entity, and the link relation type and any target attributes are carried in iCalendar property parameters. The LINK property parameters map to :rfc:`8288` attributes as follows: LABEL This parameter maps to the "title" attribute defined in Section 3.4.1 of :rfc:`8288`. LABEL is used to label the destination of a link such that it can be used as a human-readable identifier (e.g., a menu entry) in the language indicated by the LANGUAGE (if present). LANGUAGE This parameter maps to the "hreflang" attribute defined in Section 3.4.1 of :rfc:`8288`. See :rfc:`5646`. Example: ``en``, ``de-ch``. LINKREL This parameter maps to the link relation type defined in Section 2.1 of :rfc:`8288`. See `Registered Link Relation Types `_. FMTTYPE This parameter maps to the "type" attribute defined in Section 3.4.1 of :rfc:`8288`. There is no mapping for "title*", "anchor", "rev", or "media" :rfc:`8288`. Examples: The following is an example of this property, which provides a reference to the source for the calendar object. .. code-block:: ics LINK;LINKREL=SOURCE;LABEL=Venue;VALUE=URI: https://example.com/events The following is an example of this property, which provides a reference to an entity from which this one was derived. The link relation is a vendor-defined value. .. code-block:: ics LINK;LINKREL="https://example.com/linkrel/derivedFrom"; VALUE=URI: https://example.com/tasks/01234567-abcd1234.ics The following is an example of this property, which provides a reference to a fragment of an XML document. The link relation is a vendor-defined value. .. code-block:: ics LINK;LINKREL="https://example.com/linkrel/costStructure"; VALUE=XML-REFERENCE: https://example.com/xmlDocs/bidFramework.xml #xpointer(descendant::CostStruc/range-to( following::CostStrucEND[1])) Set a link :class:`icalendar.prop.uri.vUri` to the event page: .. code-block:: pycon >>> from icalendar import Event, vUri >>> from datetime import datetime >>> link = vUri( ... "http://example.com/event-page", ... params={"LINKREL":"SOURCE"} ... ) >>> event = Event.new( ... start=datetime(2025, 9, 17, 12, 0), ... summary="An Example Event with a page" ... ) >>> event.links = [link] >>> print(event.to_ical()) BEGIN:VEVENT SUMMARY:An Example Event with a page DTSTART:20250917T120000 DTSTAMP:20250517T080612Z UID:d755cef5-2311-46ed-a0e1-6733c9e15c63 LINK;LINKREL="SOURCE":http://example.com/event-page END:VEVENT LINKrU)r$linkss& r( _get_linksr|s.T HHVR E eT " " Lr*rLINKS_TYPE_SETTERc$V^8dQhRRRRRR/#)r#r$r!rrr%r:r&)r's"r(r)r)s"  Y '8 T r*c\V4VfR#\V\\\\ 34'dV.pVF7p\ V4\Jd\VRR/R7pVPRV4K9 R#)zSet the LINKs.NVALUEURI)rer) _del_linksr.rZrrrrr=)r$rlinks&& r( _set_linksrsdt }%#tT=9:: : gu%56D r*c V^8dQhRRRR/#r9r&)r's"r(r)r)sY4r*c(VPR4R#)zDelete all links.rNrCrEs&r(rrsHHVr*RELATED_TO_TYPE_SETTERc V^8dQhRRRR/#)r#r$r!r%zlist[vText | vUri | vUid]r&)r's"r(r)r) s@@)@(A@r*c\VPR.4p\V\4'gV.#V#)aRELATED-TO properties as a list. Purpose: This property is used to represent a relationship or reference between one calendar component and another. :rfc:`9523` allows URI or UID values and a GAP parameter. Value Type: :rfc:`5545`: TEXT :rfc:`9253`: URI, UID Conformance: Since :rfc:`5545`. this property can be specified in the "VEVENT", "VTODO", and "VJOURNAL" calendar components. Since :rfc:`9523`, this property MAY be specified in any iCalendar component. Description (:rfc:`5545`): The property value consists of the persistent, globally unique identifier of another calendar component. This value would be represented in a calendar component by the "UID" property. By default, the property value points to another calendar component that has a PARENT relationship to the referencing object. The "RELTYPE" property parameter is used to either explicitly state the default PARENT relationship type to the referenced calendar component or to override the default PARENT relationship type and specify either a CHILD or SIBLING relationship. The PARENT relationship indicates that the calendar component is a subordinate of the referenced calendar component. The CHILD relationship indicates that the calendar component is a superior of the referenced calendar component. The SIBLING relationship indicates that the calendar component is a peer of the referenced calendar component. Changes to a calendar component referenced by this property can have an implicit impact on the related calendar component. For example, if a group event changes its start or end date or time, then the related, dependent events will need to have their start and end dates changed in a corresponding way. Similarly, if a PARENT calendar component is cancelled or deleted, then there is an implied impact to the related CHILD calendar components. This property is intended only to provide information on the relationship of calendar components. It is up to the target calendar system to maintain any property implications of this relationship. Description (:rfc:`9253`): By default or when VALUE=UID is specified, the property value consists of the persistent, globally unique identifier of another calendar component. This value would be represented in a calendar component by the UID property. By default, the property value points to another calendar component that has a PARENT relationship to the referencing object. The RELTYPE property parameter is used to either explicitly state the default PARENT relationship type to the referenced calendar component or to override the default PARENT relationship type and specify either a CHILD or SIBLING relationship or a temporal relationship. The PARENT relationship indicates that the calendar component is a subordinate of the referenced calendar component. The CHILD relationship indicates that the calendar component is a superior of the referenced calendar component. The SIBLING relationship indicates that the calendar component is a peer of the referenced calendar component. To preserve backwards compatibility, the value type MUST be UID when the PARENT, SIBLING, or CHILD relationships are specified. The FINISHTOSTART, FINISHTOFINISH, STARTTOFINISH, or STARTTOSTART relationships define temporal relationships, as specified in the RELTYPE parameter definition. The FIRST and NEXT define ordering relationships between calendar components. The DEPENDS-ON relationship indicates that the current calendar component depends on the referenced calendar component in some manner. For example, a task may be blocked waiting on the other, referenced, task. The REFID and CONCEPT relationships establish a reference from the current component to the referenced component. Changes to a calendar component referenced by this property can have an implicit impact on the related calendar component. For example, if a group event changes its start or end date or time, then the related, dependent events will need to have their start and end dates and times changed in a corresponding way. Similarly, if a PARENT calendar component is canceled or deleted, then there is an implied impact to the related CHILD calendar components. This property is intended only to provide information on the relationship of calendar components. Deletion of the target component, for example, the target of a FIRST, NEXT, or temporal relationship, can result in broken links. It is up to the target calendar system to maintain any property implications of these relationships. Examples: :rfc:`5545` examples of this property: .. code-block:: ics RELATED-TO:jsmith.part7.19960817T083000.xyzMail@example.com .. code-block:: ics RELATED-TO:19960401-080045-4000F192713-0052@example.com :rfc:`9253` examples of this property: .. code-block:: ics RELATED-TO;VALUE=URI;RELTYPE=STARTTOFINISH: https://example.com/caldav/user/jb/cal/ 19960401-080045-4000F192713.ics See also :class:`icalendar.enums.RELTYPE`. RELATED-TOrU)r$r4s& r(_get_related_tor s.zXXlB 'F fd # #x Mr*c$V^8dQhRRRRRR/#)r#r$r!r+rr%r:r&)r's"r(r)r) s"&&)&-C&&r*c\V4VfR#\V\4'gV.pVFpVPRV4K R#)zSet the RELATED-TO properties.Nr)_del_related_tor.r/r=)r$r+r?s&& r(_set_related_tor s>D ~ fd # # u%r*cV^8dQhRR/#rrr&)r's"r(r)r) s!!)!r*c*VPRR4R#)z!Delete the RELATED-TO properties.rNrCrEs&r(rr sHH\4 r*c V^8dQhRRRR/#)r#r$r!r%z list[vUri]r&)r's"r(r)r) s)) )j)r*c\VPR.4p\V\4'gV.pV#)aCONCEPT Purpose: CONCEPT defines the formal categories for a calendar component. Conformance: Since :rfc:`9253`, this property can be specified zero or more times in any iCalendar component. Description: This property is used to specify formal categories or classifications of the calendar component. The values are useful in searching for a calendar component of a particular type and category. This categorization is distinct from the more informal "tagging" of components provided by the existing CATEGORIES property. It is expected that the value of the CONCEPT property will reference an external resource that provides information about the categorization. In addition, a structured URI value allows for hierarchical categorization of events. Possible category resources are the various proprietary systems, for example, the Library of Congress, or an open source of categorization data. Examples: The following is an example of this property. It points to a server acting as the source for the calendar object. .. code-block:: ics CONCEPT:https://example.com/event-types/arts/music .. seealso:: :attr:`icalendar.prop.categories.vCategory` CONCEPTrU)r$conceptss& r( _get_conceptsr s.Lxx 2&H h % %: Or*CONCEPTS_TYPE_SETTERc V^8dQhRRRR/#)r#r$r!rrr&)r's"r(r)r) s## #-A#r*c\V4VfR#\V\4'gV.pVFpVPRV4K R#)zSet the concepts.Nr) _del_conceptsr.r/r=)r$rr?s&& r( _set_conceptsr s?$ h % %: E"r*cV^8dQhRR/#rrr&)r's"r(r)r) s r*c*VPRR4R#)zDelete the concepts.rNrCrEs&r(rr sHHYr*c V^8dQhRRRR/#)r#rrZr]r&)r's"r(r)r) s///#/r*cZaaRV3RllpRVV3RllpRV3Rllo\W#SVR7#)zCA property for an iCalendar Property that can occur multiple times.c V^8dQhRRRR/#r%r&)r's"r(r)+multi_string_property..__annotate__ s9r*c^<VPS.4p\V\4'gV.pV#)z*Get the values of a multi-string property.rU)r$r?rs& r(rg#multi_string_property..fget s,r"%&&GE r*c$V^8dQhRRRRRR/#)r#r$r!r?zlist[str] | str | Noner%r:r&)r's"r(r)r s"""9"%;""r*c<S!V4VfR#\V\4'gV.pVFpVPSV4K R#)z*Set the values of a multi-string property.N)r.r/r=rs&&r(ro#multi_string_property..fset s> T = %&&GEE HHT5 !r*cV^8dQhRR/#rrr&)r's"r(r)r rr*c,<VPSR4R#)z-Delete the values of a multi-string property.NrCrs&r(rn#multi_string_property..fdel rr*rrv)rr]rgrornsf& @r(multi_string_propertyr s2"" D# ..r*REFIDaREFID Purpose: REFID acts as a key for associated iCalendar entities. Conformance: Since :rfc:`9253`, this property can be specified zero or more times in any iCalendar component. Description: The value of this property is free-form text that creates an identifier for associated components. All components that use the same REFID value are associated through that value and can be located or retrieved as a group. For example, all of the events in a travel itinerary would have the same REFID value, so as to be grouped together. Examples: The following is an example of this property. .. code-block:: ics REFID:itinerary-2014-11-17 Use a REFID to associate several VTODOs: .. code-block:: pycon >>> from icalendar import Todo >>> todo_1 = Todo.new( ... summary="turn off stove", ... refids=["travel", "alps"] ... ) >>> todo_2 = Todo.new( ... summary="pack backpack", ... refids=["travel", "alps"] ... ) >>> todo_1.refids == todo_2.refids True .. note:: List modifications do not modify the component. zREQUEST-STATUSaThis property defines the status code returned for a scheduling request. Setting this property replaces all existing REQUEST-STATUS values. A :class:`str` is stored as-is. Setting ``None`` or an empty list removes all REQUEST-STATUS values, as does deleting the property. The value consists of a short return status component, a longer return status description component, and optionally a status-specific data component, separated by semicolons (statcode;statdesc[;extdata]). The return status components are defined in :rfc:`5545#section-3.8.8.3`. Note: List modifications do not modify the component. Methods such as ``append()``, ``extend()``, and ``remove()``, as well as item assignment, act on a copy. Assign the list back to the property, or use :meth:`Component.add ` with a typed value instead. Parameters: request_status(str | list[str] | None): A single status string, or a list of status strings to set. Example: Add a request status to an event: .. code-block:: pycon >>> from icalendar import Event >>> event = Event.new(request_status="2.0;Success") >>> event.REQUEST_STATUS == ["2.0;Success"] True RECURRENCE_IDREQUEST_STATUS_propertyattendees_propertybusy_type_propertycategories_propertyclass_propertycolor_propertycomments_propertyconcepts_propertyconferences_propertycontacts_propertyr description_propertydescriptions_propertyr!exdates_propertyrrrur|images_propertylinks_propertylocation_propertyrwrorganizer_propertypriority_propertyrr rrrdates_propertyrefids_propertyrelated_to_propertyrepeat_propertyrfc_7953_dtend_propertyrfc_7953_dtstart_propertyrdrgrrules_propertysequence_propertyrrrrrsource_propertystatus_propertysummary_propertytransparency_property uid_property url_property)Nr)__conditional_annotations__rS __future__rrrrrtypingrrricalendar.enumsr r r r r icalendar.errorrricalendar.parser_toolsricalendar.proprrrrrrrrrricalendar.prop.conferencericalendar.prop.imagericalendar.timezonericalendar.toolsrcollections.abcrr icalendar.calr!r7r@r<r^rrKrOrNrrWrrwrrrrrrrrrrrrrrrrr X_MOZ_SNOOZE_TIME_propertyX_MOZ_LASTACK_propertyrrrr r!r2rrrr7r<r;rrIBUSY_UNAVAILABLErrTrrPUBLICrOPAQUErrrrrrr\rrrdrgsetterdeleterrur|rrrrrrrrrrrrrZr/rr rrrrrrrrrrrrrrrr__all__)rs@r(rs."..44DD@1   1&"#2']@ ! ; [AM`" L, Em`;'&+R%+BF%+P+0\)0X( "H(BFMGT  & 1 6r  / 4l& NQ f0 >4#X15C0L1L-M   ",B,<( .' 88O ' .$!N% nnnM5,1    (A>()',Za1f-   LL >4   MM (.   2& <? B) 218( =@F+ 8  "6  "  ,  ,: z,*Z+&2j/d@>D;'YKx4  02BDTUmb$J %,tC$J4E 4U/VV9  *j*= 3J$tC%K$,>,E'FF  @F&! Q)X#'tcz"2S"84"?$"FiF# ]M=I/6( +.`0"J8 8 8 8  8   8   8 8 8 8 8 8 8 8 8 8  !8 "#8 $%8 &'8 ()8 *+8 ,--8 ./8 018 238 458 6#78 898 :;8 <=8 >?8 @%A8 BC8 DE8 FG8 HI8 JK8 LM8 NO8 P Q8 R!S8 TU8 VW8 XY8 Z [8 \]8 ^_8 `a8 bc8 de8 fg8 hi8 jk8 lm8 no8 r*