i3JdZddlZddlZddlZddlmZddlmZddlmZm Z m Z m Z ddl m Z mZmZmZddlZ ddlm Z e eezZn#YnxYwerddlmZd d lmZd d lmZdd lmZmZmZdd lmZd dlmZm Z m!Z!m"Z"m#Z#d dl$m%Z%d dl&m'Z'm(Z(d dl)m*Z*m+Z+d dl,m-Z-d dl.m/Z/e ddZ0ej1dZ2Gdde%Z3Gdde%Z4Gdde%Z5Gdde5Z6Gd d!e6Z7Gd"d#e6Z8Gd$d%Z9dS)&az I'm trying to be consistent with the terminology in the RFCs: CalendarSet is a collection of Calendars Calendar is a collection of CalendarObjectResources Principal is not a collection, but holds a CalendarSet. There are also some Mailbox classes to deal with RFC6638. A SynchronizableCalendarObjectCollection contains a local copy of objects from a calendar on the server. N)datetime)sleep) TYPE_CHECKINGAnyOptionalTypeVar) ParseResult SplitResultquoteunquote)r) vCalAddress) DAVClientCalDAVSearcher)IterableIteratorSequence)Literal)CalendarObjectResourceEventFreeBusyJournalTodo) DAVObject)cdavdav)errorvcal)to_wire)URL_CCr)boundcaldavc eZdZdZdedfdZdedfdZdedfdZdedfdZ dd e dzd e dzd e dzd e dzddf d Z dd e dzd e dzd e dzd e dzddf dZ dd e dzd e dzddfdZ dS) CalendarSetz. A CalendarSet is a set of calendars. returnCalendarcBddlm}||}fd|DS)z2Convert PropfindResult list into Calendar objects.r)(_extract_calendars_from_propfind_resultsc `g|]*}tj|j|j|j+S))clienturlnameidparent)r(r,r-r.cal_id).0infoselfs L/root/projects/butler/venv/lib/python3.11/site-packages/caldav/collection.py z7CalendarSet._calendars_from_results..DsE    DKTXDI$+^b c c c   )!caldav.operations.calendarset_opsr*)r4resultsr*calendar_infoss` r5_calendars_from_resultsz#CalendarSet._calendars_from_results=s_      BA'JJ    &    r7c|jr|S|jt |j|jjd}||jS)a List all calendar collections in this set. For sync clients, returns a list of Calendar objects directly. For async clients, returns a coroutine that must be awaited. Returns: * [Calendar(), ...] Example (sync): calendars = calendar_set.get_calendars() Example (async): calendars = await calendar_set.get_calendars() rpropsdepth) is_async_client_async_calendarsr,propfindstrr-CALENDAR_LIST_PROPSr;r9r4responses r5 get_calendarszCalendarSet.get_calendarsIsj   +((** *;'' MM!@(  ++H,<===r7cK|jt|j|jjdd{V}||jS)z(Async implementation of get_calendars().rr=N)r,rBrCr-rDr;r9rEs r5rAzCalendarSet._async_calendarsasm-- MM!@.        ++H,<===r7c*|Sz Deprecated: Use :meth:`get_calendars` instead. This method is an alias kept for backwards compatibility. rGr4s r5 calendarszCalendarSet.calendarsh !!###r7Nr.r1 supported_calendar_component_setmethodc|jr|||||St|j|||||S)ax Utility method for creating a new calendar. Args: name: the display name of the new calendar cal_id: the uuid of the new calendar supported_calendar_component_set: what kind of objects (EVENT, VTODO, VFREEBUSY, VJOURNAL) the calendar should handle. Should be set to ['VTODO'] when creating a task list in Zimbra - in most other cases the default will be OK. method: 'mkcalendar' or 'mkcol' - usually auto-detected For async clients, returns a coroutine that must be awaited. Returns: Calendar(...)-object r.r0r/rOrP)r@_async_make_calendarr(r,saver4r.r1rOrPs r5 make_calendarzCalendarSet.make_calendarpse0   e,,T6;[]cdd d K-M    $f$    r7cpKt|j||||}||d{VS)&Async implementation of make_calendar.rRrSN)r(r, _async_save)r4r.r1rOrPcalendars r5rTz CalendarSet._async_make_calendarsX K-M    )))888888888r7cp|r7|s5|D] }|}||kr|cS!|r!|stjd|d|j|s4|s2|}|stjd|dS|jt d|t dttj |  t|jj r |jj |}nt|ts?t|tr[| ds| d r1|jt d |j |}nQ|jt d |t d|j t|d z}t|j|||| S) ac The calendar method will return a calendar object. If it gets a cal_id but no name, it will not initiate any communication with the server Args: name: return the calendar with this display name cal_id: return the calendar with this calendar id or URL Returns: Calendar(...)-object zNo calendar with name z found under zno calendars foundrN%Unexpected value None for self.clientz Unexpected value None for cal_idzhttps://zhttp://"Unexpected value None for self.url/)r.r0r-r/)rGget_display_namer NotFoundErrorr-r, ValueErrorrCr! objectify canonical startswithjoin isinstancer r()r4r.r1r[ display_namecalsr-s r5r[zCalendarSet.calendarsE  $ $ ..00 $ $'88:: 4''#OOO(  ^ ^%&\t&\&\RVRZ&\&\]] ] d %%''D @)*>???7N ; DEE E >?@@ @ s}V$$..00 1 1 < tJ/>>>>0>Z(8>>>>$4 +$$$$ !7;! !!Dj!d !+.* ! d !  !!!!J !7;! 99Dj9d 9+.* 9 d 9  9999"3Q3QS4Z3Qd 3Qj3Q3Q3Q3Q3Q3Qr7r&c eZdZdZ d!deddeezezezdzdedzde ddf fd Z e d"dddeezezezdzdedzddfd Z d#d edzd edzd e dzddfdZ d#d edzd edzd e dzddfdZd$dZ d!d edzd edzdedzddfdZd%dZedZejd&dZdedfdZdedfdZdZdeedzfdZd'dZd(d ZxZS)) Principala! This class represents a DAV Principal. It doesn't do much, except keep track of the URLs for the calendar-home-set, etc. A principal MUST have a non-empty DAV:displayname property (defined in Section 13.2 of [RFC2518]), and a DAV:resourcetype property (defined in Section 13.9 of [RFC2518]). Additionally, a principal MUST report the DAV:principal XML element in the value of the DAV:resourcetype property. (TODO: the resourcetype is actually never checked, and the DisplayName is not stored anywhere) Nr,rr-calendar_home_setkwargsr'c $||_tt|jd||d|||jt d|jj|_|tj }|[t dt dt d|jjz|jj tj||_dSdS)a Returns a Principal. End-users usually shouldn't need to construct Principal-objects directly. Use davclient.principal() to get the principal object of the logged-in user and davclient.principals() to get other principals. Args: client: a DAVClient() object url: The URL, if known. calendar_home_set: the calendar home set, if known If url is not given, deduct principal path as well as calendar home set path from doing propfinds. r,r-Nr]"calendar server lacking a feature:)current-user-principal property not foundz assuming %s is the principal URLrq)_calendar_home_setsuperrs__init__r,rbr- get_propertyrCurrentUserPrincipallogwarningrfr!rc)r4r,r-rtrucup __class__s r5r|zPrincipal.__init__s(#4'i'Iv3II&III ;{" !HIII{DH##C$<$>$>??C{ @AAA GHHH >PQQQ{++CM#,>,>??DHHH ;r7cK|||p|j|}||tjd{V}|Xtdtdtd|jdn1|jtj||_|S)ap Create a Principal, discovering URL if not provided. This is the recommended way to create a Principal with async clients as it handles async URL discovery. For sync clients, you can use the regular constructor: Principal(client) Args: client: A DAVClient or AsyncDAVClient instance url: The principal URL (if known) calendar_home_set: The calendar home set URL (if known) Returns: Principal with URL discovered if not provided Example (async): principal = await Principal.create(async_client) )r,r-rtNrxryz assuming z is the principal URL) r-_async_get_propertyrr~rrrfr!rc)clsr,r-rt principalrs r5createzPrincipal.creates6C!vz/   ;!55c6N6P6PQQQQQQQQC{ @AAA GHHH I IIIJJJJ &  c0B0B C C r7r.r1rOr(c||jr|||||S|j||||S)z Convenience method, bypasses the self.calendar_home_set object. See CalendarSet.make_calendar for details. For async clients, returns a coroutine that must be awaited. rOrP)r@rTrtrWrVs r5rWzPrincipal.make_calendar;sX   e,,T6;[]cdd d%33  -M 4   r7cxK|d{V}|||||d{VS)rYNr)_async_get_calendar_home_setrT)r4r.r1rOrPrts r5rTzPrincipal._async_make_calendarRss#'"C"C"E"EEEEEEE&;;  -M <         r7r&cK|jr|jS|tjd{V}|d|vrd|vrt |}||_|jS)z*Async helper to get the calendar home set.N@://)rzrrCalendarHomeSetr rtr4calendar_home_set_urls r5rz&Principal._async_get_calendar_home_setbs  " +* *&*&>&>t?S?U?U&V&V V V V V V V ! -,,,222$)*?$@$@ !!6&&r7cal_urlc|s|j||S|jtdt |j|jj|S)z The calendar method will return a calendar object. It will not initiate any communication with the server. Nr])r-)rtr[r,rbr(r-rf)r4r.r1rs r5r[zPrincipal.calendarusd L)224@@ @{" !HIIIDKT[_-A-A'-J-JKKK Kr7r c ddlm}m}|}|}|t j}||d}|||jd<|||jd<|S)zL Returns the principal, as an icalendar.vCalAddress object. r)r vTextcncutype) icalendarr rr`calendar_user_address_setr}rCalendarUserTypeparams)r4r rridsrrets r5get_vcal_addresszPrincipal.get_vcal_addresss 10000000  " " $ $,,..""4#8#:#:;;k#a&!! 599 4$uV}} 8 r7c|jsF|tj}|d|vrd|vrt |}||_|jS)Nrr)rzr}rrr rtrs r5rtzPrincipal.calendar_home_setsj& ;$($5$5d6J6L6L$M$M ! &1000!666(-.C(D(D%%:D "&&r7c6t|tr ||_dStj|}|-|jr&|j|jjjkr ||j_t|j|jj||_dSN) rgr&rzr!rchostnamer,r-rf)r4r- sanitized_urls r5rtzPrincipal.calendar_home_sets c; ' ' &)D # F c**   $% 0-*@DKOD\*\*\#0 "-dk4;?;O;OP];^;^"_"_r7c6|j|S)a] Return the principal's calendars. For sync clients, returns a list of Calendar objects directly. For async clients, returns a coroutine that must be awaited. Example (sync): calendars = principal.get_calendars() Example (async): calendars = await principal.get_calendars() )r,rGrLs r5rGzPrincipal.get_calendarss{((...r7c*|SrJrKrLs r5rMzPrincipal.calendarsrNr7ctj}|dd|dd|ddtj}tj}|d||dt j|d ||d |||| }t || }| |D]} | | d |j |j|jddi} | S)zYSends a freebusy-request for some attendee to the server as per RFC6638. prodidz-//tobixen/python-caldav//ENversionz2.0rPREQUESTuiddtstampdtstartdtenddatar0T)no_default_parametersz Content-Typeztext/calendar; charset=utf-8)headers)rr(adduuiduuid1rrnow add_componentschedule_outbox add_organizer add_attendeer,postr-r_find_objects_and_props) r4rr attendees freebusy_icalr freebusy_compoutbox caldavobjattendeerFs r5freebusy_requestzPrincipal.freebusy_requests "*,, ($BCCC)U+++(I...jll!*,, %%%%)X\^^444)W---'5)))##M222%%''-??? !!!! I IH  " "84 " H H H H;## J N#%CD$   //111r7c|tjd}|tjdd|DrJt |}|dd|DS) z$ defined in RFC6638 F) parse_propsNz,No calendar user addresses given from servercTg|]%}|jtjjk#|&Srq)tagrHrefr2xs r5r6z7Principal.calendar_user_address_set..s,EEE!QUchjjn-D-DA-D-D-Dr7cJt|dd S)N preferredr)intget)rs r5z5Principal.calendar_user_address_set..sc!%% Q*?*?&@&@%@r7)keycg|] }|j Srq)textrs r5r6z7Principal.calendar_user_address_set..s***1***r7)r}rCalendarUserAddressSetrrarpsort)r4 _addresses addressess r5rz#Principal.calendar_user_address_sets'+&7&7  ' ) )u'8' '   %&TUU UEEzEEEEEE$$  @@AAA** ****r7 ScheduleInboxc"t|S)zC Returns the schedule inbox, as defined in RFC6638 r)rrLs r5schedule_inboxzPrincipal.schedule_inboxst,,,,r7ScheduleOutboxc"t|S)zD Returns the schedule outbox, as defined in RFC6638 r)rrLs r5rzPrincipal.schedule_outboxs----r7NNNrkrj)r'r&)r'r r'N)r'r)r'r)rlrmrnrorrCr r r!rr| classmethodrrWrTrr[rpropertyrtsetterrprGrMrrrr __classcell__rs@r5rsrss5   )-<@(, #@#@%#@;  ,s 2T 9#@: #@  #@  #@#@#@#@#@#@J=A(, ***;  ,s 2T 9*: *  ***[*\ !7;   Dj d  +.*       2 !7;   Dj d  +.*       ' ' ' '* !" LLDjLd Lt L  LLLL$     ' 'X '````*/tJ///// $4 +$$$$222:+4d +;++++$---- ........r7rsceZdZdZ dcdeddeezezezdzdeddedzd edzd df fd Z dd ded Z dd ded Z fdZ dZ d eefdZded dfdZdZ dfdeededzdeded df dZdgdZdhdZdidZdjd Zdkd!Zdhd"Zdid#Zdjd$Zdld%Zdld&Z dmd'e!ed(ed e!efd)Z"dmd'e!ed(ed e!e#fd*Z$ dmd'e!ed(ed ee%eeffd+Z&d,Z' dnd/e(d0e(dzd1dd2ee)d.zd3ed e*d4f d5Z+ dod6Z, dod7Z-dpd9Z. dqd;eded?ee/j0dzd ee#f d@Z1d/e(d0e(d dAfdBZ2 drdDe*edEedFedzd edfdGZ3d edfdHZ4dIZ5dldJedzd dfdKZ6 dsdLedMe/j7dzdNed4d dfdOZ8dLed d4fdPZ9dLed d4fdQZ:dLed d4fdRZ;dtdSZdLed d4fdVZ?e=Z@d edfdWZAd edfdXZBdYed4d efdZZC dfd[edzd\ed]ed d^fd_ZDdud`ZEeEZFeDZGd edfdaZHd edfdbZIxZJS)vr(z The `Calendar` object is used to represent a calendar collection. Refer to the RFC for details: https://tools.ietf.org/html/rfc4791#section-5.3.1 Nr,rr-r0rr.r/r'c Htjd||||||d|dS)a Initialize a Calendar object. Args: client: A DAVClient instance url: The url for this calendar. May be a full URL or a relative URL. parent: The parent object (typically a CalendarSet or Principal) name: The display name for the calendar (stored in props cache) id: The calendar id (used when creating new calendars) props: A dict with known properties for this calendar )r,r-r0r/r>r.Nrq)r{r|) r4r,r-r0r.r/r>extrars r5r|zCalendar.__init__sI*  s6bD  TY     r7c|jr|||||S| ttj}||_|k|jrb|jjdt}|ddvrtj d|ddkr|dd krd }nd }nd }|j j |d z}||_ tj}|rtj|}||gz }|r4t%j} |D]} | t%j| z } || z }|d kr=|tjtjt%jgzz }tj|z} |d krtjnt%j| z} || ||d } |r| ||gdS#t:$rV |}tj||kYdS#t@!ddYYdSxYwwxYwdS)z Create a new calendar with display name `name` in `parent`. For async clients, returns a coroutine that must be awaited. Ncreate-calendar return_typesupportfullfragilequirk>Creation of calendars (allegedly) not supported on this serverr behaviourmkcol-requiredmkcol mkcalendarr_root query_methodr-expected_return_valueDcalendar server does not support display name on calendar? IgnoringTexc_info)"r@ _async_createrCrrr/r,features is_supporteddictrMkcalendarErrorr0r-rfrProp DisplayNamerSupportedCalendarComponentSetComp ResourceType Collectionr(SetMkcol Mkcalendar_queryset_properties Exceptionr`assert_rr)r4r.r/rOrP supportedpathproprhsccssccsetrrcurrent_display_names r5_createzCalendar._create/s   Z%%dB0PRXYY Y :TZ\\""B >{ & K0==>O]a=bb Y'/KKK/XY'722y7MQa7a7a$FF)FF%{##BH-- xzz  ?400L  D , 577D7 ' ' #& DLD W   C$&&#.*:*:DMOO)LL LDgii$ &' 1 1t7H7HCO KKUTY\K ] ]   ##\N33333   +/+@+@+B+B(M"6$">??????KK^!%    s$(H I  ,H::II I cK| ttj}||_|k|jrb|jjdt}|ddvrtj d|ddkr|dd krd }nd }nd }|j j |d z}||_ tj}|rtj|}||gz }|r4t!j} |D]} | t!j| z } || z }|d kr=|tjtjt!jgzz }tj|z} |d krtjnt!j| z} || ||d d{V|r ||gd{VdS#t6$rn |tjd{V} tj| |kYdS#t<ddYYdSxYwwxYwdS)z Async implementation of _create.Nrrrrrrrrrrr_rrrTr) rCrrr/r,rrrrrr0r-rfrrrrrrrrr(rrr  _async_query_async_set_propertiesr rr rr)r4r.r/rOrPrrrrhrrrrrs r5rzCalendar._async_createzs :TZ\\""B >{ & K0==>O]a=bb Y'/KKK/XY'722y7MQa7a7a$FF)FF%{##BH--xzz  ?400L  D , 577D7 ' ' #& DLD W   C$&&#.*:*:DMOO)LL LDgii$ &' 1 1t7H7HCOVS            00,@@@@@@@@@@@   151I1I#/J[J[1\1\+\+\+\+\+\+\(M"6$">??????KK^!%     s%G// I':AII#I'#I'c|jr|S|jjdt }|jjd }|ddkrt ddD]u} tn#tj $rYnwxYw | }td^#tj $rd}YnwxYw|r-|D]}|dStdS) zcDelete the calendar. For async clients, returns a coroutine that must be awaited. delete-calendarrrr333333?FN)r@_async_calendar_deleter,rrrranger{deleter DeleteError get_eventsrrasearch)r4 quirk_infowiperrs r5r zCalendar.deletesb   1..00 0[)667H$OO ;'445FGGG i I - -1b\\  GGNN$$$$(D))A#JJJJ* DEE  [[]]      GGNN     s$ B""B43B48#CC10C1cKddl}|jjdt}|jjd }|ddkrt ddD]} |d{Vn#tj$rYnwxYw | dd{V| d d{Vl#tj $rd }YnwxYw|r9| d{VD]}|d{VdS|d{VdS) z*Async implementation of Calendar.delete().rNrrrrT)eventrF) asyncior,rrrr _async_deleterr!r#rra)r4r(r$r%_objs r5rzCalendar._async_calendar_deletes[)667H$OO ;'445FGGG i I - -1b\\  ,,..........(D++D+111111111!--,,,,,,,,,,* DEE  '![[]]****** * *'')))))))))) * *$$&& & & & & & & & & &s$+BBB7CC)(C)c|jtdtjg}||d}|jrB|jD]8}|jtjj}|r|cS9gS| }|t|jj tjj}d|DS)z returns a list of component types supported by the calendar, in string format (typically ['VJOURNAL', 'VTODO', 'VEVENT']) Nr^F)parse_response_xmlc8g|]}|dS)r.)r)r2rs r5r6z5Calendar.get_supported_components..s$<<<) f%%<<rFresult components response_listrs r5get_supported_componentsz!Calendar.get_supported_componentss 8 ABB B3556&&u&GG   "* & &#.2243U3W3W3[\\ &%%%%&I!88:: WTX]334T5W5Y5Y5]^<rrr/extra_init_optionsr4rPrhs r5rUz Calendar.savesj   ,##F++ + 8 :>>*=>>L DL aDG,v a aI` a a a r7cK|j;|jd}|jd||j|d|jd{V|S)zAsync implementation of save.Nrd)r.r/rPrq)r-r>rrr/rerfs r5rZzCalendar._async_saves| 8 :>>*=>>L$$$!dgf@D@W        r7 event_urlsraise_notfoundc#K|jtdg}tjt jz}t j|zd|Dz}||dd}|t jg}|r7|j D]/}|j |} | rd| vrtj d| d|0|D]#} | || tjj fV$dS)zv get multiple events' data. TODO: Does it overlap the _request_report_build_resultlist method Nr^cBg|]}tj|jSvaluerrrr2us r5r6z&Calendar._multiget..'0\0\0\A1G1G1G0\0\0\r7report404Status  in ) r-rbrrr CalendarDataCalendarMultiGetr expand_simple_propsstatusesrrar) r4rhrirvrrrFr9hrefstatusrs r5 _multigetzCalendar._multigets5 8 ABB B xzzD-///$&&-0\0\Q[0\0\0\\;;tT844..0A0C0C/DEE  L ) L L!*40Levoo-.J.J.JD.J.JKKK 9 9Agaj!2!678 8 8 8 8 9 9r7c# K|||}|D]q\}}ttt|d}|||j|j|||VrdS)z get multiple events' data TODO: Does it overlap the _request_report_build_resultlist method? @author mtorange@gmail.com (refactored by Tobias) )riz/:@)safer-rr0N)r~r r rCr8r,r-rf)r4rhrir9r-r quoted_urls r5multigetzCalendar.multigets ..N.KK   ICws3xx00u===J9$33D99 HMM*--       r7cK|jtdtjt jz}t j|zd|Dz}||ddd{V}|t jg|r7|j D]/}|j |}|rd|vrtj d|d|0fdDS) uDAsync version of _multiget — returns a list of (url, data) tuples.Nr^cBg|]}tj|jSrlrorps r5r6z,Calendar._async_multiget..rrr7rsrtrurvcNg|]!}||tjjf"Srq)rrwr)r2rr9s r5r6z,Calendar._async_multiget..s-HHH1GAJt0456HHHr7) r-rbrrrrwrxrryrzrra) r4rhrirrrFr|r}r9s @r5_async_multigetzCalendar._async_multigets! 8 ABB BxzzD-///$&&-0\0\Q[0\0\0\\**4x@@@@@@@@..0A0C0C/DEE  L ) L L!*40Levoo-.J.J.JD.J.JKKKHHHHHHHHr7c6t|j|i|S)z get multiple events' data @author mtorange@gmail.com (refactored by Tobias) This is for backward compatibility. It may be removed in 3.0 or later release. )rprrTs r5calendar_multigetzCalendar.calendar_multigets#MDM53F33444r7VEVENTmaybestartend compfilterexpand verify_expandrctjdtd|rtjd|dkr|duo|du}|dkrt }n|dkrt }nd}|||||d }|S) a .. deprecated:: 3.0 Use :meth:`search` instead. This method will be removed in 4.0. Search events by date in the calendar. Args: start: Start of the date range to search. end: End of the date range (optional for open-ended search). compfilter: Component type to search for. Defaults to "VEVENT". Set to None to fetch all calendar components. expand: Should recurrent events be expanded? Default "maybe" becomes True unless the search is open-ended. verify_expand: Not in use anymore, kept for backward compatibility. Returns: List of CalendarObjectResource objects matching the search. Example (migrate to search):: # Legacy (deprecated): events = calendar.date_search(start, end, expand=True) # Recommended: events = calendar.search(start=start, end=end, event=True, expand=True) z7use `calendar.search rather than `calendar.date_search`) stacklevelz`verify_expand in date_search does not work anymore, as we're doing client side expansion insteadrNrVTODOF)rr comp_classrsplit_expanded)warningswarnDeprecationWarningloggingrrrr#)r4rrrrrrobjectss r5 date_searchzCalendar.date_searchsH  E       Or    W  $&:3d?F  ! !JJ 7 " "JJJ++!   r7c |jr|||||Sg}|tjg}ntjg|z}||dd}||}|D]} || } tjj| vr>| tjj} ||| n|} nd} | t} t| } | j t| } |j | |j kr|| |j|j | | || ||fS)z Takes some input XML, does a report query on a calendar object and returns the resource objects found. For async clients, returns a coroutine that must be awaited. Nrrsr-rr0r>)r@&_async_request_report_build_resultlistrrwr ryrpopr8rr!rr r-rfappendr,r4xmlrr>no_calendardatamatchesprops_rFr9rpdatacdata comp_class_r-s r5 _request_report_build_resultlistz)Calendar._request_report_build_resultlistFs   >>Z  ='))*FF'))*U2F;;sAx00..v66  AAJE $-- $"3"788@J@RD55e<<| tjj} ||| n|} nd} | t} t| } | j t| } |j | |j kr| | |j|j | | || ||fS)z9Async implementation of _request_report_build_resultlist.Nrrsr)rrwrryrrr8rr!rr r-rfrr,rs r5rz/Calendar._async_request_report_build_resultlistys ='))*FF'))*U2F**38<<<<<<<<..v66  AAJE $-- $"3"788@J@RD55e<<c ddlm} t| ddtsJ| } | D]} | ddksJ| } | dkrd} | d krd } | d krd } | d krIt| d t r | d g| d <| d D]}| ||y| dks | | jvrt| | | | | dr'| | dd| | d| | | | |s|r|}|j r| |||||||S| |||||||S)aBSends a search request towards the server, processes the results if needed and returns the objects found. Refactoring 2025-11: a new class class:`caldav.search.CalDAVSearcher` has been made, and this method is sort of a wrapper for CalDAVSearcher.search, ensuring backward compatibility. The documentation may be slightly overlapping. I believe that for simple tasks, this method will be easier to use than the new interface, hence there are no plans for the foreseeable future to deprecate it. This search method will continue working as it has been doing before for all foreseeable future. I believe that for simple tasks, this method will be easier to use than to construct a CalDAVSearcher object and do searches from there. The refactoring was made necessary because the parameter list to `search` was becoming unmanagable. Advanced searches should be done via the new interface. Caveat: The searching is done on the server side, the RFC is not very crystal clear on many of the corner cases, and servers often behave differently when presented with a search request. There is planned work to work around server incompatibilities on the client side, but as for now complicated searches will give different results on different servers. ``todo`` - searches explicitly for todo. Unless ``include_completed`` is specified, there is some special logic ensuring only pending tasks is returned. There is corresponding ``event`` and ``journal`` bools to specify that the search should be only for events or journals. When neither are set, one should expect to get all objects returned - but quite some calendar servers will return nothing. This will be solved client-side in the future, as for 2.0 it's recommended to search separately for tasks, events and journals to ensure consistent behaviour across different calendar servers and providers. ``sort_keys`` refers to (case-insensitive) properties in the icalendar object, ``sort_reverse`` can also be given. The sorting will be done client-side. Use ``start`` and ``end`` for time-range searches. Open-ended searches are supported (i.e. "everything in the future"), but it's recommended to use closed ranges (i.e. have an "event horizon" of a year and ask for "everything from now and one year ahead") and get the data expanded. With the boolean ``expand`` set, you don't have to think too much about recurrences - they will be expanded, and with the (default) ``split_expanded`` set, each recurrence will be returned as a separate list object (otherwise all recurrences will be put into one ``VCALENDAR`` and returned as one ``Event``). This makes it safe to use the ``event.component`` property. The non-expanded resultset may include events where the timespan doesn't match the date interval you searched for, as well as items with multiple components ("special" recurrences), meaning you may need logic on the client side to handle the recurrences. *Only time range searches over closed time intervals may be expanded*. As for 2.0, the expand-logic is by default done on the client-side, for consistent results across various server incompabilities. However, you may force server-side expansion by setting ``server_expand=True`` Text attribute search parameters can be given to query the "properties" in the calendar data: category, uid, summary, comment, description, location, status. According to the RFC, a substring search should be done. You may use no_category, no_summary, etc to search for objects that are missing those attributes. Negated text matches are not supported yet. For power-users, those parameters are also supported: * ``xml`` - use this search query, and ignore other filter parameters * ``comp_class`` - alternative to the ``event``, ``todo`` or ``journal`` booleans described above. * ``filters`` - other kind of filters (in lxml tree format) rrrTrr*rrrrrrrrrrNrr) r#rrgrboolrCrrrrerr@ async_search)r4rrrrr>filters post_filter_hacksrrrrrrs r5r#zCalendar.searchs F +******..488$?????%n&&  H HCq6S====Ehm##'k!!"k!!j5s;;H/9+/F.GJ{+)+6G,,WlCCC $${/O(O(O S*S/:::!!%(( H//abb :c?U\/]]]]//z#GGGG w C   ++m^UCf !! -[&   r7rctjtj||gz}||dd}t ||jS)z Search the calendar, but return only the free/busy information. Args: start : defaults to datetime.today(). end : same as above. Returns: [FreeBusy(), ...] rrs)r FreeBusyQuery TimeRanger rraw)r4rrrrFs r5rzCalendar.freebusy_requestgsM!##t~eS'A'A&BB;;tQ11hl+++r7duepriorityrinclude_completedsort_keyc<|r|f}|d||S)a Fetches a list of todo items (this is a wrapper around search). For sync clients, returns a list of Todo objects directly. For async clients, returns a coroutine that must be awaited. Args: sort_keys: use this field in the VTODO for sorting (iterable of lower case string, i.e. ('priority','due')). include_completed: boolean - by default, only pending tasks are listed sort_key: DEPRECATED, for backwards compatibility with version 0.4. Example (sync): todos = calendar.get_todos() Example (async): todos = await calendar.get_todos() T)todorr)r#)r4rrrs r5 get_todoszCalendar.get_todosws/.  $! I{{8IU^{___r7c|j|i|S)z Deprecated: Use :meth:`get_todos` instead. This method is an alias kept for backwards compatibility. )rrTs r5todoszCalendar.todoss t~u////r7c:|tSt|dri|dD]R}|}|dkr tcS|dkr t cS|dkr t cS|dkr tcSSnt|drt|j stStjttjt tjt tjti}|j D]}|j |vr||j cStS) z takes some data, either as icalendar text or icalender object (TODO: consider vobject) and returns the appropriate CalendarResourceObject child class. Nsplit z BEGIN:VEVENTz BEGIN:VTODOzBEGIN:VJOURNALzBEGIN:VFREEBUSY subcomponents) rhasattrrstriprrrrlenrrr)r4rline ical2caldavscs r5r8z%Calendar._calendar_comp_class_by_datas: <* ) 4 ! ! 5 4(( $ $zz||>)) LLL=((KKK+++"NNN,,,#OOO- $T? + + 5t)** .--!7"H K ( 5 5<;..&r|4444/%%r7rcJt|||S)z7 Returns the event with the given URL. r)rload)r4r|rs r5 event_by_urlzCalendar.event_by_urls%D666;;===r7r comp_filterrc|||dd}fd|D}|stjdztjt |dk|dS)a> Get one calendar object from the calendar by UID. Args: uid: the object uid comp_class: filter by component type (Event, Todo, Journal) comp_filter: for backward compatibility. Don't use! Returns: CalendarObjectResource (Event, Todo, or Journal) Tinsist)rrrrrc*g|]}|jk |Srq)r/)r2rPrs r5r6z.Calendar.get_object_by_uid..s ===Qqr7z%s not found on serverrr)r#rrar r)r4rrr items_founds ` r5get_object_by_uidzCalendar.get_object_by_uids2kk V^"  >===+===  F%&>&DEE E c+&&!+,,,1~r7cT||tjdS)z Get a task/todo from the calendar by UID. Returns the task with the given uid. See :meth:`get_object_by_uid` for more details. rrrr CompFilterr4rs r5get_todo_by_uidzCalendar.get_todo_by_uids'%%ctw7O7O%PPPr7cT||tjdS)z Get an event from the calendar by UID. Returns the event with the given uid. See :meth:`get_object_by_uid` for more details. rrrrs r5get_event_by_uidzCalendar.get_event_by_uids'%%ctx7P7P%QQQr7cT||tjdS)z Get a journal entry from the calendar by UID. Returns the journal with the given uid. See :meth:`get_object_by_uid` for more details. VJOURNALrrrs r5get_journal_by_uidzCalendar.get_journal_by_uids'%%ctz7R7R%SSSr7c|j|i|S)z Deprecated: Use :meth:`get_object_by_uid` instead. This method is an alias kept for backwards compatibility. )rrTs r5 object_by_uidzCalendar.object_by_uids &t%u7777r7c,||S)z Deprecated: Use :meth:`get_event_by_uid` instead. This method is an alias kept for backwards compatibility. )rrs r5 event_by_uidzCalendar.event_by_uids $$S)))r7c,||S)z Deprecated: Use :meth:`get_todo_by_uid` instead. This method is an alias kept for backwards compatibility. )rrs r5 todo_by_uidzCalendar.todo_by_uids ##C(((r7c,||S)z Deprecated: Use :meth:`get_journal_by_uid` instead. This method is an alias kept for backwards compatibility. )rrs r5journal_by_uidzCalendar.journal_by_uids &&s+++r7c8|tS)ay List all events from the calendar. For sync clients, returns a list of Event objects directly. For async clients, returns a coroutine that must be awaited. Returns: * [Event(), ...] Example (sync): events = calendar.get_events() Example (async): events = await calendar.get_events() r)r#rrLs r5r"zCalendar.get_events*s${{e{,,,r7c*|S)z Deprecated: Use :meth:`get_events` instead. This method is an alias kept for backwards compatibility. )r"rLs r5eventszCalendar.events>s    r7rcFddl}g}|D]}t|drUtjj|jvr=|t|jtjjgt|dr9|t|j | d |}| | d}d|S) a  Generate a fake sync token for servers without sync support. Uses a hash of all ETags to detect changes. Args: objects: List of calendar objects to generate token from Returns: A fake sync token string rNr>r-|F)usedforsecurityfake-)hashlibrrGetEtagrr>rrCr-rdrrfmd5encode hexdigest)r4rretagsr+combined hash_values r5_generate_fake_sync_tokenz"Calendar._generate_fake_sync_tokenFs  7 7CsG$$ 7CI)E)E S3;?!;<<====e$$ 7 S!2!2!4!455666 88E??[[!2!2E[JJTTVV #z###r7 sync_token load_objectsdisable_fallback&SynchronizableCalendarObjectCollectionc& d}|jjdt}|ddkr|rt jdd}|r,t|tr| drd}|rm tj }tj | }tj d }tjtjz} |||| gz} || tjgd \} } | j}n>#| jd tj jzd j}YnxYw|r/| D],} | #t j$rY)wxYwt1|| |S#t jt jf$r+}|rt4d|dYd}~nd}~wwxYwt4dt;|}|rG|D]D} t?| dr| j + | /#t j$rY@wxYwE|rt?|d drtjj|d j!vrt |"tjgd} | #tjg}d|D}t4dtI|d|%D]\}} t|j&'|(}||vr`t?||ds i||_!||j!)| t4d|n4#tT$r'}t4d|Yd}~nd}~wwxYw|+|}|rBt|tr-| dr||krt1|g|St1|||S)aget_objects_by_sync_token aka get_objects Do a sync-collection report, ref RFC 6578 and https://github.com/python-caldav/caldav/issues/87 This method will return all objects in the calendar if no sync_token is passed (the method should then be referred to as "objects"), or if the sync_token is unknown to the server. If a sync-token known by the server is passed, it will return objects that are added, deleted or modified since last time the sync-token was set. If load_objects is set to True, the objects will be loaded - otherwise empty CalendarObjectResource objects will be returned. This method will return a SynchronizableCalendarObjectCollection object, which is an iterable. This method transparently falls back to retrieving all objects if the server doesn't support sync tokens. The fallback behavior is identical from the user's perspective, but less efficient as it transfers the entire calendar on each sync. If disable_fallback is set to True, the method will raise an exception instead of falling back to retrieving all objects. This is useful for testing whether the server truly supports sync tokens. Tz sync-tokenrr unsupportedz+Sync tokens are not supported by the serverFrrm1)r>rz.//r)r[rrzSync-collection REPORT failed (z!), falling back to full retrievalNz6Using fallback sync mechanism (retrieving all objects)_datar>r)r?c\i|])}t|j|*Srq)rCr-rdr2r+s r5 z6Calendar.get_objects_by_sync_token..s0SSSc#'"3"3"5"566SSSr7zFallback: Fetching ETags for z objectszFallback: Added ETag to z)Failed to fetch ETags for fallback sync: ),r,rrrrr ReportErrorrgrCrerSyncCollection SyncToken SyncLevelrrrrtreefindallrrrrarDAVErrorrr3debugrpr#rrr>_query_propertiesryritemsr-rfrdupdater r)r4rrruse_sync_token sync_supportcmdtokenlevelr>rrFrr+e all_objects etag_props url_to_objurl_strcanonical_url_strfake_sync_tokens r5get_objects_by_sync_tokenz"Calendar.get_objects_by_sync_token_s(D{+88SW8XX   I & &- 7 7 W'(UVVV"N  #*Z55 #*:O:OPW:X:X #"N  a a(** J777 C000 S[]]2eUE22&*&K&K'L''#7Z!)!4JJZ!)!6!6us}?P7P!Q!QRS!T!YJJJ !&!!!HHJJJJ$2!!! D!>!7z%u~6 a a a#_1___````````  a JKKK4;;==))   "  sG,, 0A  .1B   A00 47KO;WX>K_4_4_ 113;==/1KK%993;==/JJ TS{SSS  S#j//SSSTTT&0&6&6&8&8RRNGU(+DHMM',B,B,L,L,N,N(O(O%(J66&z2C'DgNNEBDJ'89?"#45;BB5III "P=N"P"PQQQ R    IaIIJJJ  88EE  *Z55 *:O:OPW:X:X _,,=!2/6;?    s BF/&D.-F/.9E)' F/3FF/FF/FF//G5 !G00G5I&&I87I85D>O44 P%>P  P%c|j|i|S)z Deprecated: Use :meth:`get_objects_by_sync_token` instead. This method is an alias kept for backwards compatibility. )r2rTs r5objects_by_sync_tokenzCalendar.objects_by_sync_tokens .t-u????r7c8|tS)zd List all journals from the calendar. Returns: * [Journal(), ...] r)r#rrLs r5 get_journalszCalendar.get_journalss{{g{...r7c*|S)z Deprecated: Use :meth:`get_journals` instead. This method is an alias kept for backwards compatibility. )r6rLs r5journalszCalendar.journalss   """r7)NNNNNNrjr)NFF)FF)r'r)r'r)r'r)r'rGr)F)NrrF)NNF)r'r)NFTFNNNN)rFNrk)r'r)r'r)KrlrmrnrorrCr r r!r|rrr rrprr4r<rCtyperrrQrNrVrXrZr\r^r`rbrUrZrr~r"rtuplerrrrrrrrrrrwr#rrrr8rrrrrrrrrrr'r"rrr2r4r get_objectsr6r8rrs@r5r(r(s.)-<@(,  % ;  ,s 2T 9 %  Dj  $J         4QUI IIIIXQU; ;;;;z@'''6=$s)====0 c D       " "//y/ / Dj /// "////b88887777::::11110000////2222&99HSM949T\]`Ta999908C=$S[\_S`$AFII"3-I9=I eCHo IIII$555 $#*1# CCC_C C ww'' C  C * +CCCCRAF1#1#1#1#hAF$#$#$#$#L0000h##"04T T T T  T  T D%&- T  cT T T T l,h,X,*,,,,$$7"'# ``C=` `* ` f ````<0f0000"&"&"&H>>sTz>W>>>>/39= !! !_t+!56 !  !!!!FQ3Q+CQQQQRCR,DRRRRTcT.FTTTT8888**(@****)s)'?)))),#,*B,,,, E-DM----(!W !!!!$6N1O$TW$$$$6"&"!& L L $JL L  L 2 L L L L \@@@@$G+K/d9o////#$y/########r7r(c leZdZdZ d deddedzdeezeze zdzddffd Z d Z xZ S) ScheduleMailboxaw RFC6638 defines an inbox and an outbox for handling event scheduling. TODO: As ScheduleMailboxes works a bit like calendars, I've chosen to inheritate the Calendar class, but this is a bit incorrect, a ScheduleMailbox is a collection, but not really a calendar. We should create a common base class for ScheduleMailbox and Calendar eventually. Nr,rrr-r'ctt|||d|_|s|r |j|_|s$|r"|jt d|jj}|D|t d|jtj ||_dS|t d|jt d|j|_ |jjt| | |_dS#tjddtj|jd|_tjd t%| d tjxYw) z9 Will locate the mbox if no url is given rwNr]z Unexpected value None for clientz#Unexpected value None for principalzsomething bad happenedTrzprincipal has no z. )r{r=r|_itemsr,rbrr-rfr!rcr}findproprrr check_scheduling_supportrarC ERR_FRAGMENT)r4r,rr-rs r5r|zScheduleMailbox.__init__s ot$$--V-EEE  +) +#*DK .V .{" !HIII -I ?~ !CDDDzs}S'9'9::DHHH  !FGGG{" !HIII }DH  ;?//D4E4Edmmoo4V4V0W0WXX  6FFFF dkBBDDEEE))25dmmoo2F2F2F2FHZHZ[s#AD;;B Gc0js d_n#tjdt jdt jvfdD_jD]}| YnhxYw j nJ#fdD_jD]}| YnxYwjS)z_ TODO: work in progress TODO: perhaps this belongs to the super class? TrzXcaldav server does not seem to support a sync-token REPORT query on a scheduling mailboxgooglecHg|]}t|djSr)r-r,rr,r2rr4s r5r6z-ScheduleMailbox.get_items..O:MN*qtDKHHHr7cHg|]}t|djSrGrHrIs r5r6z-ScheduleMailbox.get_items..XrJr7) r?rrr"rr rCr-childrenrsync)r4rs` r5 get_itemszScheduleMailbox.get_itemsBs[ {  "lll==   n h#dh--7888RVR_R_RaRa AFFHHHH    """" RVR_R_RaRa AFFHHHH{s&BB)-CADr) rlrmrnrorrsrCr r r!r|rNrrs@r5r=r= s)-&*<@ ++%+t#+;  ,s 2T 9 +  ++++++Zr7r=ceZdZejZdS)rN)rlrmrnrScheduleInboxURLr@rqr7r5rrgs$HHHr7rceZdZejZdS)rN)rlrmrnrScheduleOutboxURLr@rqr7r5rrks%HHHr7rc`eZdZdZd dZdeefdZdefdZ dZ de eeffdZ dS) rz This class may hold a cached snapshot of a calendar, and changes in the calendar can easily be copied over through the sync method. To create a SynchronizableCalendarObjectCollection object, use calendar.objects(load_objects=True) r'Nc>||_||_||_d|_dSr)r[rr_objects_by_url)r4r[rrs r5r|z/SynchronizableCalendarObjectCollection.__init__xs%  $ #r7c4|jSr)r__iter__rLs r5rWz/SynchronizableCalendarObjectCollection.__iter__~s|$$&&&r7c*t|jSr)rrrLs r5__len__z.SynchronizableCalendarObjectCollection.__len__s4<   r7cx|j-i|_|D]#}||j|j<$|jS)zp returns a dict of the contents of the SynchronizableCalendarObjectCollection, URLs -> objects. )rUr-rd)r4r+s r5objects_by_urlz5SynchronizableCalendarObjectCollection.objects_by_urlsM   '#%D  @ @.s(RRR3cg//113RRRr7r)rgrrCrer[r2r[r-rdrrrr>rrrrarrpvaluesrrUrr!rr"r#r$rrr) r4 updated_objs deleted_objs is_fake_tokenupdatesobur+current_objectscurrent_by_url old_by_urlr-old_datanew_datas r5rMz+SynchronizableCalendarObjectCollection.syncs  #4?C88`T_=W=WX_=`=` $ %" %-AAO%B g0#6687;M;X;XY`;a;a8$(MM--//C&--"%'"3"3"5"5GsNN # 3sw<3E E E # 39 < <"37|1#+/BciPSP[P_F``` ('*CG -HHJJJ(//4444$2---(//444GGCG,,,,,-$( #5#5DL+/D(&-&8DO(,771"2%u~6 % % % $  % ' T IIM N N N#4=#7#7#9#9::O'  HHJJJJ*DSR/RRRN,,..J+0022 - -S*$$8?z#PV7W7Waz#33]aH+23+?+?IsxxTH8++0D$++C000!'',,,," 9 9n,, '' 3888  5 5 7 788DL#'D "mEEdlSSDOl++sHD$H")F  H >G H G?HH/.H/:JJ! J!r) rlrmrnror|rrrWrrYr[r:rMrqr7r5rros$$$$ '(3-''''!!!!!$$$],eCHo],],],],],],r7r):rorrrrtimertypingrrrr urllib.parser r r r rdate TimeStampr davclientrr#rcollections.abcrrrrcalendarobjectresourcerrrrr davobjectrelementsrrlibrrlib.python_utilitiesr lib.urlr!r" getLoggerrr&rsr(r=rrrrqr7r5rws   888888888888AAAAAAAAAAAA )II D'%%%%%%$$$$$$&&&&&&8888888888! )))))) ge3444g!!_Q_Q_Q_Q_Q)_Q_Q_QDr.r.r.r.r. r.r.r.j x#x#x#x#x#yx#x#x#v'SSSSShSSSz%%%%%O%%%&&&&&_&&&|,|,|,|,|,|,|,|,|,|,s A A