U j)@sdZddlmZddlZddlmZddlmZmZmZm Z ddl m Z m Z m Z mZmZmZddlZddlZddlmZmZmZmZmZmZmZmZmZmZmZddl m!Z!dd l"m#Z#m$Z$dd l%m&Z&m'Z'm(Z(m)Z)m*Z*dd l+m,Z,dd l-m.Z.m/Z/m0Z0m1Z1m2Z2m3Z3m4Z4dd l5m6Z6m7Z7ddl8m9Z9m:Z:e r:ddl;me!ddddZ?gZ@Gddde!ZAe1fddddddddd ZBed!d"ZCed#d$ZDdd%d&d'd(ZEdd%d)d*d+ZFdd,d-d.ZGd/ZHGd0d1d1eAZIGd2d3d3eAZJGd4d5d5eAZKGd6d7d7eAZLGd8d9d9eAZMGd:d;d;eAZNGdd?d?eAZPGd@dAdAeAZQe.ZRe>ZSdBd?dAddd1d7dCd5d9d=d;d3dDdgZTdS)EzCalendar is a dictionary like Python object that can render itself as VCAL files according to RFC 5545. These are the defined components. ) annotationsN) defaultdict)datedatetime timedeltatzinfo) TYPE_CHECKINGList NamedTupleOptionalTupleUnion) categories_propertycolor_propertyexdates_propertymulti_language_text_propertyrdates_propertyrrules_propertysequence_propertysingle_int_propertysingle_string_propertysingle_utc_property uid_property) CaselessDict)IncompleteComponentInvalidCalendar) Contentline Contentlines Parametersq_joinq_split)DEFAULT_ENCODING) TypesFactorytzid_from_tzinfo vDDDLists vDDDTypes vDurationvText vUTCOffset)TZPtzp)is_date to_datetimeAlarmsstrbytes)component_directory example_namereturnc Cstjt}tj|d|}|ds.|d}tj||}tj|sntd|d|ddt|t |d}| W5QRSQRXdS) z5Return an example and raise an error if it is absent.testsz.icszExample z for z not found. You can use one of , rbN) ospathdirname__file__joinendswithisfile ValueErrorlistdiropenread)r1r2hereZexamplesZ example_filefrD1/tmp/pip-unpacked-wheel-g40nyxg1/icalendar/cal.py get_example2s     rFcs eZdZdZfddZZS)ComponentFactoryz~All components defined in RFC 5545 are registered in this factory class. To get a component you can use it like this. csZtj||t|d<t|d<t|d<t|d<t|d<t|d<t|d<t |d<t |d <d S) #Set keys to upper for initial dict.VEVENTVTODOVJOURNAL VFREEBUSY VTIMEZONESTANDARDDAYLIGHTVALARM VCALENDARN) super__init__EventTodoJournalFreeBusyTimezoneTimezoneStandardTimezoneDaylightAlarmCalendarselfargskwargs __class__rDrErSJszComponentFactory.__init__)__name__ __module__ __qualname____doc__rS __classcell__rDrDrarErGEsrG) CATEGORIES RESOURCESFREEBUSYcs>eZdZdZdZdZdZdZdZdZ dZ fddZ ddZ e Z d d Zed=d d Zd>ddZddZefddZd?ddZd@ddZddddZddZdddfdd d!d"ZdAd$d d%d&ZedBd'd(ZedCd*d+ZdDd,d-ZdEd.d/ZdFd0d1Z d2d3Z!fd4d5Z"e#d6d7Z$e#d8d9Z%d:d d;d<Z&Z'S)G ComponentzComponent is the base object for calendar, Event and the other components defined in RFC 5545. Normally you will not use this class directly, but rather one of the subclasses. NrDFcstj||g|_g|_dS)rHN)rRrS subcomponentserrorsr]rarDrErSxszComponent.__init__cCsdS)zAReturns True, CaselessDict would return False if it had no items.TrDr^rDrDrE__bool__szComponent.__bool__cCst||jsdSdS)zDReturns True if Component has no items or subcomponents, else False.TF)listvaluesrmrorDrDrEis_emptyszComponent.is_emptyrhcCs~|s|St|tjr|}nt|}||}|rzt|dsBt|_|D].\}}|dkrn||jkrx|j|=qJ||j|<qJ|S)aEncode values to icalendar property values. :param name: Name of the property. :type name: string :param value: Value of the property. Either of a basic Python type of any of the icalendar's own property types. :type value: Python native type or icalendar property type. :param parameters: Property parameter dictionary for the value. Only available, if encode is set to True. :type parameters: Dictionary :param encode: True, if the value should be encoded to one of icalendar's own property types (Fallback is "vText") or False, if not. :type encode: Boolean :returns: icalendar property value paramsN) isinstance types_factoryZ all_types for_propertyhasattrrrtitems)namevalue parametersencodeobjklasskeyitemrDrDrE_encodes      zComponent._encodecst|tr dkr t|}rTt|trTdkrTfdd|D}n|}kr}t|trt|tr||}q|||}n||g}|<dS)aAdd a property. :param name: Name of the property. :type name: string :param value: Value of the property. Either of a basic Python type of any of the icalendar's own property types. :type value: Python native type or icalendar property type. :param parameters: Property parameter dictionary for the value. Only available, if encode is set to True. :type parameters: Dictionary :param encode: True, if the value should be encoded to one of icalendar's own property types (Fallback is "vText") or False, if not. :type encode: Boolean :returns: None )Zdtstampcreatedz last-modified)ZrdateZexdate categoriescsg|]}|qSrDr.0vr}rzr|r^rDrE sz!Component.add..N)rurlowerr*Z localize_utcrqrappend)r^rzr{r|r}ZoldvalrDrrEadds&      z Component.addcCs2t|tr|St||}t|tr.|t}|S)z&Internal for decoding property values.)rur$rv from_icalr'r}r!)r^rzr{decodedrDrDrE_decodes     zComponent._decodecsTkr:}t|tr.fdd|DS|S|tkrLtn|SdS)z"Returns decoded value of property.csg|]}|qSrDrrrzr^rDrErsz%Component.decoded..N)rurqr_markerKeyError)r^rzdefaultr{rDrrEr s   zComponent.decodedcs2ddtD}|r.fdd|DS|S)z*Returns a list of values (split on comma).cSsg|]}|dqS)z" )striprrDrDrErsz(Component.get_inline..csg|]}|qSrDrrvalrrDrEr!s)r )r^rzdecodevalsrDrrE get_inlineszComponent.get_inlinecs0|rfdd|D}tdt|<dS)z^Converts a list of values into comma separated string and sets value to that. csg|]}j|ddqS)rhr}r)rr{rrDrEr)sz(Component.set_inline..inlineN)rvr)r^rzrrr}rDrrE set_inline$szComponent.set_inline componentcCs|j|dS)z%Add a subcomponent to this component.N)rmr)r^rrDrDrE add_component/szComponent.add_componentcCsHg}|dks|j|kr(||r(|||jD]}||||7}q.|S)zWalk to given component.N)rzrrm_walk)r^rzselectresult subcomponentrDrDrEr3s   zComponent._walkcCsdS)NTrD)crDrDrE<zComponent.zlist[Component]r3cCs|dk r|}|||S)aRecursively traverses component and subcomponents. Returns sequence of same. If name is passed, only components with name will be returned. :param name: The name of the component or None such as ``VEVENT``. :param select: A function that takes the component as first argument and returns True/False. :returns: A list of components that match. :rtype: list[Component] N)upperr)r^rzrrDrDrEwalk<s zComponent.walkTzlist[tuple[str, object]]c Cstd}d||jfg}|r*|}n|}|D]>}||}t|trf|D]}|||fqPq6|||fq6|r|jD]} || j |d7}q|d||jf|S)z`Returns properties in this component and subcomponents as: [(name, value), ...] textBEGINsortedEND) rvrzto_icalZ sorted_keyskeysrurqrrmproperty_items) r^ recursiverr'Z propertiesZproperty_namesrzrrr{rrDrDrErMs    zComponent.property_itemsc sg}g}t|D]T}|sqz|\}}WnZtk r}z<|rN|dnd} | r\| js^| jdt|fWYqW5d}~XYnX|} | dkr|} t | t } | } t | dds| | _ || q| dkr2|std|} |s|| n|d| |dkrhd | krht| qt||rJ|dnd} | sv| d krfqjntd |d d } z|dkr|d}d krfdd|D}nfdd|D}n<|| krd kr|d g}n|g}WnBtk rD}z"| js | j| t|fW5d}~XYqX|D]}|_| j||ddqJq|rt|St|dkrt|d|t|dkrt|d||dS)z2Populates the component recursively from a string.Nrrzrz.END encountered without an accompanying BEGIN!rMTZIDz X-COMMENTz Property "z#" does not have a parent component.)DTSTARTDTEND RECURRENCE-IDDUERDATEEXDATErk,cs g|]}|dqSrrrfactoryrtrDrErsz'Component.from_ical..csg|]}|qSrDrr)rrDrErsrrrh3Found multiple components where only one is allowed1Found no components where exactly one is required)rrpartsr>ignore_exceptionsrnrr/rcomponent_factorygetrlgetattrrzpoprr*Zcache_timezone_componentrvrwsplitrtrlen _format_error)clsstmultiplestackcompslinerzrerunameZc_nameZc_classZdatetime_namesZparsed_componentsZparsed_componentrDrrErgs               &zComponent.from_ical[...]cCsbd}t|t|t||krP|t|t|}|d|d|d|S|d|SdS)Naz:  )r)Zerror_descriptionZ bad_inputZelipsisZmax_error_lengthZ truncate_torDrDrErs zComponent._format_errorcCs t|dt}tj||||dS)z!Returns property as content line.rtr)rrrZ from_parts)r^rzr{rrtrDrDrE content_lineszComponent.content_linecCsDt}|j|dD]"\}}|j|||d}||q|d|S)zString representation of class with all of it's subcomponents.r5css|]}t|VqdSN)r/)ritrDrDrE sz%Component.__repr__..(r))r;rmrztypercdict)r^subsrDrDrE__repr__szComponent.__repr__csLt|jt|jkrdSt|}|s,dS|jD]}||jkr2dSq2dS)NFT)rrmrR__eq__)r^otherZproperties_equalrrarDrErs   zComponent.__eq__DTSTAMPa@RFC 5545: Conformance: This property MUST be included in the "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar components. Description: In the case of an iCalendar object that specifies a "METHOD" property, this property specifies the date and time that the instance of the iCalendar object was created. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property specifies the date and time that the information associated with the calendar component was last revised in the calendar store. The value MUST be specified in the UTC time format. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property is equivalent to the "LAST-MODIFIED" property. LAST-MODIFIEDaRFC 5545: Purpose: This property specifies the date and time that the information associated with the calendar component was last revised in the calendar store. Note: This is analogous to the modification date and time for a file in the file system. Conformance: This property can be specified in the "VEVENT", "VTODO", "VJOURNAL", or "VTIMEZONE" calendar components. boolcCstdd|DS)zXWhether this component has attributes that indicate that Mozilla Thunderbird created it.css|]}|dVqdS)zX-MOZ-N) startswith)rattrrDrDrEr;sz+Component.is_thunderbird..)anyrrorDrDrEis_thunderbird9szComponent.is_thunderbird)Nrh)Nrh)rh)rh)TT)F)r)T)T)T)(rcrdrerfrzrequired singletonsr exclusive inclusiverrSrp __nonzero__rs staticmethodrrrrrrrrrrr classmethodrrrrrrrrrZ LAST_MODIFIEDrrgrDrDrarErlesR  ( 7     r   rl Optional[str]z tuple[type]r)prop value_attr value_typetype_defdocvPropc sddfdd }dddfdd }t||jd <|jd <ddfd d d d|ddddDd}t|||S)awCreate a single property getter and setter. :param prop: The name of the property. :param value_attr: The name of the attribute to get the value from. :param value_type: The type of the value. :param type_def: The type of the property. :param doc: The docstring of the property. :param vProp: The type of the property from :mod:`icalendar.prop`. rlrocst}||}||krdSt|tr8tdddkrD|n t||}t|stddddDd|d|S) Nz Multiple z defined.z must be either a  or css|] }|jVqdSrrcrtrDrDrEr^sz8create_single_property..p_get.., not .)objectrrurqrrr;)r^rrr{)rrrrDrEp_getTs   $z%create_single_property..p_getNoner^r3cs|dkr|dSt|sJtddddDdt|jd||<|jkr|jD]}|krf||dqfdS)NzUse rcss|] }|jVqdSrrrrDrDrErhsz8create_single_property..p_set..rr)ru TypeErrorr;rrcrr)r^r{Z other_prop)p_delrrrrDrEp_setbs &   z%create_single_property..p_setr{r3cs|dSrrro)rrDrErtsz%create_single_property..p_delzThe z property. z Accepted values: r5css|] }|jVqdSrrrrDrDrEr{sz)create_single_property..z. If the attribute has invalid values, we raise InvalidCalendar. If the value is absent, we return None. You can also delete the value with del or by setting it to None. )r __annotations__r;property) rrrrrrrrZp_docrD)rrrrrrEcreate_single_propertyBs r zX-MOZ-SNOOZE-TIMEz1Thunderbird: Alarms before this time are snoozed.z X-MOZ-LASTACKz6Thunderbird: Alarms before this time are acknowledged.zOptional[timedelta]rcCs^t}|d|}t|tr"|jSt|tr2|jS||k rZt|tsZtdt |j ddS)zGetter for property DURATION.durationz"DURATION must be a timedelta, not rN) rrrur%dtr&tdrrrrc)r^rr rDrDrE _get_durations   rr^r{cCs\|dkr|dddSt|ts8tdt|jdt||d<|d|ddS)zSetter for property DURATION.Nr zUse timedelta, not rrr)rrurrrrcr&rrDrDrE _set_durations    rrocCs|ddS)zDelete property DURATION.DURATIONNrrorDrDrE _del_durationsraThe DURATION property. The "DTSTART" property for a "{component}" specifies the inclusive start of the event. 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@seZdZdZdZdZdZdZdZdZ dZ e d d d d Z e d)dddddZeddeefedZeddeefedZddZe eeeejddZe dd ddZe dd ddZejd d!d"dZe dd d#d$Zejd%d&d'd$ZeZ e!Z"e#Z$e%Z&e'Z(e)Z*e+Z,e-Z.e/Z0d(S)*rTa A "VEVENT" calendar component is a grouping of component properties that represents a scheduled amount of time on a calendar. For example, it can be an activity, such as a one-hour long department meeting from 8:00 AM to 9:00 AM, tomorrow. rI) SUMMARYrrrrUIDrSEQUENCERRULErrrr)CLASSCREATEDCOLOR DESCRIPTIONrGEOrLOCATION ORGANIZERPRIORITYrrSTATUSrZTRANSPURLrrrr)rr ATTACHATTENDEEriCOMMENTCONTACTrRSTATUSRELATEDrjrrTr.rcCsddlm}||S)aQCompute the alarm times for this component. >>> from icalendar import Event >>> event = Event.example("rfc_9074_example_1") >>> len(event.alarms.times) 1 >>> alarm_time = event.alarms.times[0] >>> alarm_time.trigger # The time when the alarm pops up datetime.datetime(2021, 3, 2, 10, 15, tzinfo=ZoneInfo(key='America/New_York')) >>> alarm_time.is_active() # This alarm has not been acknowledged True Note that this only uses DTSTART and DTEND, but ignores RDATE, EXDATE, and RRULE properties. rr-icalendar.alarmsr.r^r.rDrDrEalarmss z Event.alarmsrfc_9074_example_3r/rzr3cCs|td|S)0Return the calendar example with the given name.eventsrrFrrzrDrDrEexamplesz Event.examplerr zQThe "DTSTART" property for a "VEVENT" specifies the inclusive start of the event.rzdThe "DTEND" property for a "VEVENT" calendar component specifies the non-inclusive end of the event.cCs|j}|j}|j}|dk r*|dk r*tdt|trXt|tsX|dk rX|jdkrXtd|dk r|dk rt|t|krtd|||fS)=Verify the calendar validity and return the right attributes.Nz>> from datetime import datetime >>> from icalendar import Event >>> event = Event() >>> event.start = datetime(2021, 1, 1, 12) >>> event.end = datetime(2021, 1, 1, 12, 30) # 30 minutes >>> event.duration # 1800 seconds == 30 minutes datetime.timedelta(seconds=1800) >>> print(event.to_ical()) BEGIN:VEVENT DTSTART:20210101T120000 DTEND:20210101T123000 END:VEVENT rNNo DTSTART given.r;rr^r9rDrDrEr9Ms z Event.startOptional[date | datetime]r9cCs ||_dSzSet the start.Nrr@rDrDrEr9hscCsl|\}}}|dkrH|dkrH|dkr.tdt|rD|tddS|S|dk rh|dk r`||Std|S)The end of the component. Invalid values raise an InvalidCalendar error. If there is no end, we also raise an IncompleteComponent error. Nz#No DTEND or DURATION+DTSTART given.rhdaysr;rr+rr8rDrDrEr:msz Event.enddate | datetime | Noner:cCs ||_dSz Set the end.N)rr^r:rDrDrEr:sN)r.)1rcrdrerfrzcanonical_orderrrrrrr r-rr4r rrrrr;rrr _doc_durationformatrr r9setterr:_X_MOZ_SNOOZE_TIMEX_MOZ_SNOOZE_TIME_X_MOZ_LASTACK X_MOZ_LASTACKrcolorrsequencerrrrdatesrexdatesrrrulesruidrDrDrDrErTsh  rTc@seZdZdZdZdZdZdZdZe dde e fe d Z e d de e fe d Z eeeeejdd Zd dZeddddZejddddZeddddZejddddZeddddZeZeZedddd ZeZ e!Z"e#Z$e%Z&e'Z(e)Z*e+Z,d!S)"rUa- A "VTODO" calendar component is a grouping of component properties that represents an action item or assignment. For example, it can be used to represent an item of work assigned to an individual, such as "Prepare for the upcoming conference seminar on Internet Calendaring". rJr)rrZ COMPLETEDrrrrrrrrzPERCENT-COMPLETEr rrr!rrr"rr)rrr#rr zOThe "DTSTART" property for a "VTODO" specifies the inclusive start of the Todo.rz`The "DUE" property for a "VTODO" calendar component specifies the non-inclusive end of the Todo.rcCs|j}|j}|j}|dk r*|dk r*tdt|trXt|tsX|dk rX|jdkrXtd|dk r|dk rt|t|krtd|||fS)r5Nz9Only one of DUE and DURATION may be in a VTODO, not both.rr6zBDTSTART and DUE must be of the same type, either date or datetime.) rrrrrurrr7r+r8rDrDrEr;s. zTodo._get_start_end_durationr=rcCs |d}|dkrtd|S)aThe start of the VTODO. Invalid values raise an InvalidCalendar. If there is no start, we also raise an IncompleteComponent error. You can get the start, end and duration of a Todo as follows: >>> from datetime import datetime >>> from icalendar import Todo >>> todo = Todo() >>> todo.start = datetime(2021, 1, 1, 12) >>> todo.end = datetime(2021, 1, 1, 12, 30) # 30 minutes >>> todo.duration # 1800 seconds == 30 minutes datetime.timedelta(seconds=1800) >>> print(todo.to_ical()) BEGIN:VTODO DTSTART:20210101T120000 DUE:20210101T123000 END:VTODO rNr>r?r@rDrDrEr9s z Todo.startrArBcCs ||_dSrCrDr@rDrDrEr9scCsl|\}}}|dkrH|dkrH|dkr.tdt|rD|tddS|S|dk rh|dk r`||Std|S)rENz!No DUE or DURATION+DTSTART given.rhrFrHr8rDrDrEr:szTodo.endrIrJcCs ||_dSrK)rrLrDrDrEr:)srcCs |j|jS)zThe duration of the VTODO. This duration is calculated from the start and end of the Todo. You cannot set the duration as it is unclear what happens to start and end. r<rorDrDrEr .sz Todo.durationr.cCsddlm}||S)aCompute the alarm times for this component. >>> from datetime import datetime >>> from icalendar import Todo >>> todo = Todo() # empty without alarms >>> todo.start = datetime(2024, 10, 26, 10, 21) >>> len(todo.alarms.times) 0 Note that this only uses DTSTART and DUE, but ignores RDATE, EXDATE, and RRULE properties. rr-r*r,rDrDrEr-:s z Todo.alarmsN)-rcrdrerfrzrrrrr rrrrr rrrrNrOrr;r9rPr:r rQrRrSrTr-rrUrrVrrrrWrrXrrYrrZrDrDrDrErUs`  rUc@seZdZdZdZdZdZdZedde e fe dZ e d d d d Z e jd dddd Z e Ze dd ddZeZeZeZeZeZeZeZdS)rVaA descriptive text at a certain time or associated with a component. A "VJOURNAL" calendar component is a grouping of component properties that represent one or more descriptive text notes associated with a particular calendar date. The "DTSTART" property is used to specify the calendar date with which the journal entry is associated. Generally, it will have a DATE value data type, but it can also be used to specify a DATE-TIME value data type. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day. rKr) rrrrrrrrrr!rrr") r$r%rir&r'rr)rrr(rrr zjThe "DTSTART" property for a "VJOURNAL" that specifies the exact date at which the journal entry was made.rrcCs|j}|dkrtd|S)zThe start of the Journal. The "DTSTART" property is used to specify the calendar date with which the journal entry is associated. Nr>)rrr@rDrDrEr9sz Journal.startzdatetime | dater)r{r3cCs ||_dS)zSet the start of the journal.NrDrrDrDrEr9srcCstdS)z*The journal has no duration: timedelta(0).rrrorDrDrEr szJournal.durationN)rcrdrerfrzrrrr rrrr r9rPr:r rrUrrVrrrrWrrXrrYrrZrDrDrDrErVUs4 rVc@s$eZdZdZdZdZdZdZeZ dS)rWa A "VFREEBUSY" calendar component is a grouping of component properties that represents either a request for free or busy time information, a reply to a request for free or busy time information, or a published set of busy time information. rLr)r'rrrrrr")r%r&rkr(N) rcrdrerfrzrrrrrZrDrDrDrErWs  rWc @sheZdZUdZded<dZdZdZdZe dddZ e d ddZ e d;d d d ddZ edd dddZeddZedfdddddZed dddZddd d!Zd"d#d$Ded%d&edd&ed'd(ed)d(edd(ed'd*ed)d*edd*gZe d+e e fd,d-d.d.dd/d0d1Ze ee e fd dd.d.dd2d3d4Zed5dd6d7Zed8dd9d:Zd+S).rcSsg|]}|jD] }|jqqSrD)Zdtsr )rtreeZleafrDrDrErscsg|]}|fqSrDrD)r transtimeZ offsetfromZoffsettor^rDrErsrNrrOrh) TZOFFSETFROM TZOFFSETTOrintr7rrGdateutiltztzoffsetrdrrrrulerrulestrr*Zfix_rrule_untilrurqsetrz) rr^rcZ offsetto_sZ offsetfrom_sZtziZrrstartrornZ transtimesrW transitionsZis_dstrDrgrE_extract_offsetss8    zTimezone._extract_offsetscCs ||kr|d7}q|||S)zW :param tzname: Candidate tzname :param tznames: Other tznames Z_1)r)r^tznamesrDrDrE_make_unique_tzname!s  zTimezone._make_unique_tznameTr)r)r* lookup_tzidcCs&|r||j}|dk r|S||S)aconvert this VTIMEZONE component to a timezone object :param tzp: timezone provider to use :param lookup_tzid: whether to use the TZID property to look up existing timezone definitions with tzp. If it is False, a new timezone will be created. If it is True, the existing timezone will be used if it exists, otherwise a new timezone will be created. N)timezonetz_nameZcreate_timezone)r^r*rurlrDrDrEto_tz-s  zTimezone.to_tzrcCs8zt|dWStk r2|dddYSXdS)zReturn the name of the timezone component. Please note that the names of the timezone are different from this name and may change with winter/summer time. rasciirdN)r/UnicodeEncodeErrorr}rorDrDrErw=szTimezone.tz_namez=Tuple[List[datetime], List[Tuple[timedelta, timedelta, str]]]c Cs |j}g}i}t}|D]}t|tkr0qt|djrNt|dj|_t |djt sft dzt |d}Wnt k r|ddd}|||}Yn`tk r|d|ddd|dd|d }|||}YnX|||\||<}||q|d d |D}g} t|D]\} \} } } }d }||srtd d}nt| dddD].}|||ds| ||d}qq|st| t|D].}|||ds| ||d}qq|d k st | | ||fqH|| fS)zReturn a tuple of (transition_times, transition_info) - transition_times = [datetime, ...] - transition_info = [(TZOFFSETTO, dts_offset, tzname)] rzEVTIMEZONEs sub-components' DTSTART must be of type datetime, not dateTZNAMEryrd_rbrhricSsg|]\}}}}||qSrDrD)rrfosfromr|rDrDrErrs z,Timezone.get_transitions..Frr7rhr)rwrprrrXr+r r,rrurAssertionErrorr/rzr}rtrrrrrextendsort enumeraterrangerr)r^zonerqdstrsrr^Zcomponent_transitionsZtransition_timesZtransition_infonumrfr}ZostorzZ dst_offsetindexrDrDrEget_transitionsIsn         zTimezone.get_transitionscCsg|]}t|dqS)rFr[)rrGrDrDrErszTimezone.)@ rrhr)hours)minutesr~Nrrr)rvtzid first_date last_dater3c CsV|dkr(t|}|dkr(td|dt|ddd}t|j|j|j}t|j|j|j}t|dr|||}||}n|j |d}|j |d}t t }|} d} | |kr~| } | } | } |j D]Z} | }|| | } z"| | kr| }|| | } qWntk rYq YnX|} q| tk}| }|dkrHt| }| | ||f}||| j dd|| |j d } q|}|d ||d d |d |d|D]\\} } }}}t|}||||krt|j|j|j}|rtnt}| dkr| } | |_| |_|d|||_|rD|d|||q|S)aReturn a VTIMEZONE component from a timezone object. This works with pytz and zoneinfo and any other timezone. The offsets are calculated from the tzinfo object. Parameters: :param tzinfo: the timezone object :param tzid: the tzid for this timezone. If None, it will be extracted from the tzinfo. :param first_date: a datetime that is earlier than anything that happens in the calendar :param last_date: a datetime that is later than anything that happens in the calendar :raises ValueError: If we have no tzid and cannot extract one. .. note:: This can take some time. Please cache the results. NzCannot get TZID from z . Please set the tzid parameter. normalizecSs|SrrD)r rDrDrErrz&Timezone.from_tzinfo..localizerarrr&zThis timezone only works from z to rr{r)r#r>rryearmonthdayrxrrdrrq utcoffset_from_tzinfo_skip_search OverflowErrorrrr^r/rrryminremoverrYrZrhrirr)rrvrrrrZfirst_datetimeZ last_datetimeoffsetsr9Z offset_toZ offset_fromr:Z add_offsetZlast_endZ is_standardrzrrlr^ZstartsZ first_startrrDrDrE from_tzinfost                 zTimezone.from_tzinfo)rr*rrr3cCs2||}|dkr"td|d|||||S)aCreate a VTIMEZONE from a tzid like ``"Europe/Berlin"``. :param tzid: the id of the timezone :param tzp: the timezone provider :param first_date: a datetime that is earlier than anything that happens in the calendar :param last_date: a datetime that is later than anything that happens in the calendar :raises ValueError: If the tzid is unknown. >>> from icalendar import Timezone >>> tz = Timezone.from_tzid("Europe/Berlin") >>> print(tz.to_ical()[:36]) BEGIN:VTIMEZONE TZID:Europe/Berlin .. note:: This can take some time. Please cache the results. NzUnkown timezone r)rvr>r)rrr*rrrlrDrDrE from_tzids zTimezone.from_tzidzlist[TimezoneStandard]cCs |dS)z%The STANDARD subcomponents as a list.rNrrorDrDrEstandardszTimezone.standardzlist[TimezoneDaylight]cCs |dS)z_The DAYLIGHT subcomponents as a list. These are for the daylight saving time. rOrrorDrDrEdaylight"szTimezone.daylight)r\)rcrdrerfr rzrMrrr_DEFAULT_FIRST_DATE_DEFAULT_LAST_DATErr4rrrrtr*rxr rwrrrrrrrrDrDrDrErXsZ   5  J\rXc@sfeZdZdZdZdZdZdZedde fe dZ edd e fe d e Z ed d e fe d e ZeZeZeZd S)rYz The "STANDARD" sub-component of "VTIMEZONE" defines the standard time offset from UTC for a time zone. It represents a time zone's standard time, typically used during winter months in locations that observe Daylight Saving Time. rN)rrirh)r&rr{rrrr zThe mandatory "DTSTART" property gives the effective onset date and local time for the time zone sub-component definition. "DTSTART" in this usage MUST be specified as a date with a local time value.rirzThe mandatory "TZOFFSETTO" property gives the UTC offset for the time zone sub-component (Standard Time or Daylight Saving Time) when this observance is in use. rhaThe mandatory "TZOFFSETFROM" property gives the UTC offset that is in use when the onset of this time zone observance begins. "TZOFFSETFROM" is combined with "DTSTART" to define the effective onset for the time zone sub-component definition. For example, the following represents the time at which the observance of Standard Time took effect in Fall 1967 for New York City: DTSTART:19671029T020000 TZOFFSETFROM:-0400 N)rcrdrerfrzrrrr rrrr(rirhrrWrrXrrYrDrDrDrErY+s>   rYc@sDeZdZdZdZejZejZejZej Z ej Z ej Z e Z eZeZdS)rZa  The "DAYLIGHT" sub-component of "VTIMEZONE" defines the daylight saving time offset from UTC for a time zone. It represents a time zone's daylight saving time, typically used during summer months in locations that observe Daylight Saving Time. rON)rcrdrerfrzrYrrrrrirhrrWrrXrrYrDrDrDrErZgsrZc@seZdZdZdZdZdZdZdZe ddd Z e e e ed Zed d Zed deefeeeefdZe ddddZejddddZGdddeZe ddZedejdZdS)r[z A "VALARM" calendar component is a grouping of component properties that defines an alarm or reminder for an event or a to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do. rP)ACTIONTRIGGER) r$rrrrrREPEATrZ PROXIMITY ACKNOWLEDGED))rr)rr%)r%r$z RELATED-TOrra!The REPEAT property of an alarm component. The alarm can be defined such that it triggers repeatedly. A definition of an alarm with a repeating trigger MUST include both the "DURATION" and "REPEAT" properties. The "DURATION" property specifies the delay period, after which the alarm will repeat. The "REPEAT" property specifies the number of additional repetitions that the alarm will be triggered. This repetition count is in addition to the initial triggering of the alarm. aBThe DURATION property of an alarm component. The alarm can be defined such that it triggers repeatedly. A definition of an alarm with a repeating trigger MUST include both the "DURATION" and "REPEAT" properties. The "DURATION" property specifies the delay period, after which the alarm will repeat. raThis is defined in RFC 9074: Purpose: This property specifies the UTC date and time at which the corresponding alarm was last sent or acknowledged. This property is used to specify when an alarm was last sent or acknowledged. This allows clients to determine when a pending alarm has been acknowledged by a calendar user so that any alerts can be dismissed across multiple devices. It also allows clients to track repeating alarms or alarms on recurring events or to-dos to ensure that the right number of missed alarms can be tracked. Clients SHOULD set this property to the current date-time value in UTC when a calendar user acknowledges a pending alarm. Certain kinds of alarms, such as email-based alerts, might not provide feedback as to when the calendar user sees them. For those kinds of alarms, the client SHOULD set this property when the alarm is triggered and the action is successfully carried out. When an alarm is triggered on a client, clients can check to see if an "ACKNOWLEDGED" property is present. If it is, and the value of that property is greater than or equal to the computed trigger time for the alarm, then the client SHOULD NOT trigger the alarm. Similarly, if an alarm has been triggered and an "alert" has been presented to a calendar user, clients can monitor the iCalendar data to determine whether an "ACKNOWLEDGED" property is added or changed in the alarm component. If the value of any "ACKNOWLEDGED" property in the alarm changes and is greater than or equal to the trigger time of the alarm, then clients SHOULD dismiss or cancel any "alert" presented to the calendar user. rr a2Purpose: This property specifies when an alarm will trigger. Value Type: The default value type is DURATION. The value type can be set to a DATE-TIME value type, in which case the value MUST specify a UTC-formatted DATE-TIME value. Either a positive or negative duration may be specified for the "TRIGGER" property. An alarm with a positive duration is triggered after the associated start or end of the event or to-do. An alarm with a negative duration is triggered before the associated start or end of the event or to-do.r/rcCs$|d}|dkrdS|jddS)aThe RELATED parameter of the TRIGGER property. Values are either "START" (default) or "END". A value of START will set the alarm to trigger off the start of the associated event or to-do. A value of END will set the alarm to trigger off the end of the associated event or to-do. In this example, we create an alarm that triggers two hours after the end of its parent component: >>> from icalendar import Alarm >>> from datetime import timedelta >>> alarm = Alarm() >>> alarm.TRIGGER = timedelta(hours=2) >>> alarm.TRIGGER_RELATED = "END" rNSTARTr))rrt)r^triggerrDrDrETRIGGER_RELATEDs zAlarm.TRIGGER_RELATED)r{cCs(|d}|dkrtd||jd<dS)zSet "START" or "END".rNzrt)r^r{rrDrDrErs  c@s*eZdZUdZded<ded<ded<dS)zAlarm.TriggerszThe computed times of alarm triggers. start - triggers relative to the start of the Event or Todo (timedelta) end - triggers relative to the end of the Event or Todo (timedelta) absolute - triggers at a datetime in UTC ztuple[timedelta]r9r:ztuple[datetime]absoluteN)rcrdrerfr rDrDrDrETriggerss  rcCsg}g}g}|j}|dk rt|tr4|||}n(|jdkrN|||}n|||}|j}|dk rt|jD]}||d|qt|jt |t |t |dS)aThe computed triggers of an Alarm. This takes the TRIGGER, DURATION and REPEAT properties into account. Here, we create an alarm that triggers 3 times before the start of the parent component: >>> from icalendar import Alarm >>> from datetime import timedelta >>> alarm = Alarm() >>> alarm.TRIGGER = timedelta(hours=-4) # trigger 4 hours before START >>> alarm.DURATION = timedelta(hours=1) # after 1 hour trigger again >>> alarm.REPEAT = 2 # trigger 2 more times >>> alarm.triggers.start == (timedelta(hours=-4), timedelta(hours=-3), timedelta(hours=-2)) True >>> alarm.triggers.end () >>> alarm.triggers.absolute () Nrr)r9r:r) rrurrrrrrrtuple)r^r9r:rrrr r|rDrDrEtriggerss,     zAlarm.triggersrz X-ALARMUIDN) rcrdrerfrzrrrrrrr rrrrrrr rrr r rrrPr rrrrrZrDrDrDrEr[|sP     +r[c@seZdZdZdZdZdZdZdZe d/ddd d d Z e d0d dZ e ddddZ e ddddZe ddddZddddZddddZe dddd Zejejfd!d!d"d#d$Zed%d&d'Zed(d)d*Zed+d,d-ZeZeZd.S)1r\z The "VCALENDAR" object is a collection of calendar information. This information can include a variety of components, such as "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY", "VTIMEZONE", or any other type of calendar component. rQ)VERSIONPRODIDCALSCALEMETHODr X-WR-CALDESCNAME X-WR-CALNAME)rr)rrrrr)rirrr4r/r/cCs|td|S)r0Z calendarsr2r3rDrDrEr4uszCalendar.exampleFcCstj|dd}d}|D]:}|jD].}|jdkrJ|r4qNt||Sq d}q q|rZ|St|dkrvt|d|t|dkrt|d||dS) NT)rrMFrhrrr)rlrrmrzrr>r)rrrrZall_timezones_so_farcomprrDrDrErzs,     zCalendar.from_icalz list[Event]rcCs |dS)aAll event components in the calendar. This is a shortcut to get all events. Modifications do not change the calendar. Use :py:meth:`Component.add_component`. >>> from icalendar import Calendar >>> calendar = Calendar.example() >>> event = calendar.events[0] >>> event.start datetime.date(2022, 1, 1) >>> print(event["SUMMARY"]) New Year's Day rIrrorDrDrEr1szCalendar.eventsz list[Todo]cCs |dS)zAll todo components in the calendar. This is a shortcut to get all todos. Modifications do not change the calendar. Use :py:meth:`Component.add_component`. rJrrorDrDrEtodosszCalendar.todoszlist[FreeBusy]cCs |dS)zAll FreeBusy components in the calendar. This is a shortcut to get all FreeBusy. Modifications do not change the calendar. Use :py:meth:`Component.add_component`. rLrrorDrDrEfreebusyszCalendar.freebusyzset[str]cCsBt}|jddD]$\}}t|dr||jdq|dhS)aThe set of TZIDs in use. This goes through the whole calendar to find all occurrences of timezone information like the TZID parameter in all attributes. >>> from icalendar import Calendar >>> calendar = Calendar.example("timezone_rdate") >>> calendar.get_used_tzids() {'posix/Europe/Vaduz'} Even if you use UTC, this will not show up. FrrtrN)rprrxrrtr)r^rrzr{rDrDrEget_used_tzidss  zCalendar.get_used_tzidscCs$|}|jD]}||jq|S)zThe set of missing timezone component tzids. To create a :rfc:`5545` compatible calendar, all of these timezones should be added. )rr]rrw)r^ZtzidsrvrDrDrEget_missing_tzidss zCalendar.get_missing_tzidszlist[Timezone]cCs |dS)a>Return the timezones components in this calendar. >>> from icalendar import Calendar >>> calendar = Calendar.example("pacific_fiji") >>> [timezone.tz_name for timezone in calendar.timezones] ['custom_Pacific/Fiji'] .. note:: This is a read-only property. rMrrorDrDrEr]s zCalendar.timezonesrrrc CsJ|D]<}ztj|||d}Wntk r8YqYnX||qdS)aAdd all missing VTIMEZONE components. This adds all the timezone components that are required. .. note:: Timezones that are not known will not be added. :param first_date: earlier than anything that happens in the calendar :param last_date: later than anything happening in the calendar >>> from icalendar import Calendar, Event >>> from datetime import datetime >>> from zoneinfo import ZoneInfo >>> calendar = Calendar() >>> event = Event() >>> calendar.add_component(event) >>> event.start = datetime(1990, 10, 11, 12, tzinfo=ZoneInfo("Europe/Berlin")) >>> calendar.timezones [] >>> calendar.add_missing_timezones() >>> calendar.timezones[0].tz_name 'Europe/Berlin' >>> calendar.get_missing_tzids() # check that all are added set() rN)rrXrr>r)r^rrrrvrDrDrEadd_missing_timezoness   zCalendar.add_missing_timezonesrraThis property specifies the name of the calendar. This implements :rfc:`7986` ``NAME`` and ``X-WR-CALNAME``. Property Parameters: IANA, non-standard, alternate text representation, and language property parameters can be specified on this property. Conformance: This property can be specified multiple times in an iCalendar object. However, each property MUST represent the name of the calendar in a different language. Description: This property is used to specify a name of the iCalendar object that can be used by calendar user agents when presenting the calendar data to a user. Whilst a calendar only has a single name, multiple language variants can be specified by including this property multiple times with different "LANGUAGE" parameter values on each. Example: Below, we set the name of the calendar. .. code-block:: pycon >>> from icalendar import Calendar >>> calendar = Calendar() >>> calendar.calendar_name = "My Calendar" >>> print(calendar.to_ical()) BEGIN:VCALENDAR NAME:My Calendar END:VCALENDAR rraThis property specifies the description of the calendar. This implements :rfc:`7986` ``DESCRIPTION`` and ``X-WR-CALDESC``. Conformance: This property can be specified multiple times in an iCalendar object. However, each property MUST represent the description of the calendar in a different language. Description: This property is used to specify a lengthy textual description of the iCalendar object that can be used by calendar user agents when describing the nature of the calendar data to a user. Whilst a calendar only has a single description, multiple language variants can be specified by including this property multiple times with different "LANGUAGE" parameter values on each. Example: Below, we add a description to a calendar. .. code-block:: pycon >>> from icalendar import Calendar >>> calendar = Calendar() >>> calendar.description = "This is a calendar" >>> print(calendar.to_ical()) BEGIN:VCALENDAR DESCRIPTION:This is a calendar END:VCALENDAR raThis property specifies a color used for displaying the calendar. This implements :rfc:`7986` ``COLOR`` and ``X-APPLE-CALENDAR-COLOR``. Please note that since :rfc:`7986`, subcomponents can have their own color. 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 Calendar >>> calendar = Calendar() >>> calendar.color = "black" >>> print(calendar.to_ical()) BEGIN:VCALENDAR COLOR:black END:VCALENDAR zX-APPLE-CALENDAR-COLORN)r4)F) rcrdrerfrzrMrrrrr4rr r1rrrrr]rXrrrrZ calendar_name descriptionrrUrrrrZrDrDrDrEr\QsP     (&!"&r\INLINErr)Urf __future__rr7 collectionsrrrrrtypingrr r r r r Zdateutil.rrulerkZ dateutil.tzZicalendar.attrrrrrrrrrrrrZicalendar.caselessdictrZicalendar.errorrrZicalendar.parserrrrrr Zicalendar.parser_toolsr!Zicalendar.propr"r#r$r%r&r'r(Zicalendar.timezoner)r*Zicalendar.toolsr+r,r+r.rFrGrrrlr rQrSrrrrNrTrUrVrWrXrYrZr[r\rvr__all__rDrDrDrEs   4  $  fA  [E\ \<V7