i7rdZddlZddlZddlZddlZddlZddlmZddlmZm Z m Z ddl m Z m Z mZddlmZmZddlZddlmZddlmZmZ dd l mZmZeeezZn#YnxYwe r dd lmZd d lmZdd lmZmZddl mZej dkrddl!m"Z"nddl m"Z"ddl#m$Z$d dl%m&Z&m'Z'm(Z(m)Z)m*Z*d dl+m,Z,d dl-m.Z.m/Z/d dl0m1Z1m2Z2d dl3m4Z4d dl5m6Z6m7Z7m8Z8d dl9m:Z:d dl;mGdde,Z?Gdde?Z@Gdd e?ZAGd!d"e?ZBGd#d$e?ZCdS)%a Calendar Objects Resources, as defined in the RFC 4791. There are three subclasses Todo, Journal and Event. Those mirrors objects stored on the server. The word ``CalendarObjectResource`` is long, complicated and may be hard to understand. When you read the word "event" in any documentation, issue discussions, etc, then most likely it should be read as "a CalendarObjectResource, like an event, a task or a journal". Do not make the mistake of going directly to the Event-class if you want to contribute code for handling "events" - consider that the same code probably will be appicable to Joural and Todo events, if so, CalendarObjectResource is the right class! Clear as mud? FreeBusy is also defined as a Calendar Object Resource in the RFC, and it is a bit different . Perhaps there should be another class layer between CalendarObjectResource and Todo/Event/Journal to indicate that the three latter are closely related, while FreeBusy is something different. Alarms and Time zone objects does not have any class as for now. Those are typically subcomponents of an event/task/journal component. Users of the library should not need to construct any of those objects. To add new content to the calendar, use ``calendar.add_event``, ``calendar.add_todo`` or ``calendar.add_journal``. Those methods will return a CalendarObjectResource. To update an existing object, use ``event.save()``. N) defaultdict)datetime timedeltatimezone) TYPE_CHECKINGAnyOptional) ParseResult SplitResult)rrulestr) vCalAddressvText)ClassVarr )r ) DAVClient)Callable Container)Literal) )Self)contextmanager) DataStateIcalendarState NoDataState RawDataState VobjectState) DAVObject)cdavdav)errorvcal)errmsg) to_normal_str to_unicodeto_wire)URL) _quote_uidcaldavceZdZUdZddddddZeed<d Zd Zd Z d Z d Z e d zed <d Z eed <ed ed zfdZejded zd d fdZ dydeddeezezezd zded zded zded zded zd d ffd ZdzdZd{dZd eefdZd|dededed d fd Z d} d{d!Z d~d"e!ed zd#e"egefd zd$ed%ed e#ee$eff d&Z%d'Z&d e'fd(Z( dd)ed*ed+ed efd,Z)dzd+ed ee'fd-Z*dzd+ed efd.Z+dzd/Z,d{d0Z-ee,e-d12Z.e.Z/d3Z0e0Z1dzd4ed d fd5Z2d efd6Z3d efd7Z4dd8ed9d d fd:Z5dd8ed9d d fd;Z6dd8ed zd d fd<Z7d{d=Z8dd>ed?ed zd efd@Z9dzdAed efdBZ:dzdAed efdCZ;d efdDZd|dGZ?d|dHZ@dd{dIZAdd{dJZBdKZCddLed zd d fdMZD ddNedOedPed zdQedRedSedTed efdUZEd efdVZFdWZGd efdXZHd efdYZIdZZJd[ZKd\ZLeeKeJd]2ZMeed<eeLeJd^2ZNddaZOd ed`fdbZPd ed`fdcZQdddZReePeOde2ZSdfedg<eeQeRdh2ZTdfedi<djZUdkZVeeVeUdl2ZWeedm<d e fdnZXd efdoZYd eZj[fdpZ\ddqZ]e^drZ_e^dsZ`d ed zfdtZad ed zfduZbd efdvZcd edfdwZedxZfxZgS)CalendarObjectResourceaKRef RFC 4791, section 4.1, a "Calendar Object Resource" can be an event, a todo-item, a journal entry, or a free/busy entry As per the RFC, a CalendarObjectResource can at most contain one calendar component, with the exception of recurrence components. Meaning that event.data typically contains one VCALENDAR with one VEVENT and possibly one VTIMEZONE. In the case of expanded calendar date searches, each recurrence will (by default) wrapped in a distinct CalendarObjectResource object. This is a deviation from the definition given in the RFC. CHILDPARENTSIBLING FINISHTOSTART DEPENDENT)r-r,r.z DEPENDS-ONr/RELTYPE_REVERSE_MAPN_stateF _borrowedreturnc|}|:|jr3|jjD]&}|jdvrd|vrt |d}n'|S)a/Returns the UID of the calendar object. Extracts the UID from the calendar data using cheap accessors that avoid unnecessary parsing (issue #515, #613). Falls back to direct icalendar parsing if the cheap accessor fails. Does not trigger a load from the server. N)VEVENTVTODOVJOURNALUID)_get_uid_cheap_icalendar_instance subcomponentsnamestr)selfuidcomps X/root/projects/butler/venv/lib/python3.11/site-packages/caldav/calendarobjectresource.pyidzCalendarObjectResource.idish!!## ;43;0>  9 ???ETMMd5k**CE valuecdS)zSetter exists for compatibility with parent class __init__. The actual UID is stored in the calendar data, not separately. Setting this is a no-op - modify the icalendar data directly. N)r?rEs rBrCzCalendarObjectResource.id{s  rDclientrurldataparentrCpropscXtt|||||||u||_|rn|r\|jdd}|jd|d|_t|j |_ dSdSdSdS)z CalendarObjectResource has an additional parameter for its constructor: * data = "...", vCal data for the event )rHrIrKrCrLNr9) superr+__init__rJ_get_component_type_cheapicalendar_componentpopadd_datarr;r2) r?rHrIrJrKrCrLold_id __class__s rBrOzCalendarObjectResource.__init__s $d++44s6b 5     DI Gd4466 G155eTBB(,,UB777! ,T-EFF    G G G GrDc|j}t|dr&|js|tj}|}|dd||jd|r4|r2d|vr.|d| d||z | |j|dS)acThe RFC specifies that a VEVENT/VTODO cannot have both dtend/due and duration, so when setting dtend/due, the duration field must be evicted WARNING: this method is likely to be deprecated and parts of it moved to the icalendar library. If you decide to use it, please put caldav<4.0 in the requirements. tzinfoDURATIONNDTSTART) rQhasattrrX astimezonerutc get_durationrR _ENDPARAMrS)r?end move_dtstartidurations rBset_endzCalendarObjectResource.set_ends  $ 3 ! ! /#* /....C$$&& j$ dnd###  -H -a EE)    EE)S8^ , , , dnc"""""rDc|jtd|j}|jd|dS)z goes via self.client, finds the principal, figures out the right attendee-format and adds an organizer line to the event N%Unexpected value None for self.client organizer)rH ValueError principalrQrSget_vcal_address)r?ris rB add_organizerz$CalendarObjectResource.add_organizers[ ; DEE EK))++   $$[)2L2L2N2NOOOOOrDctjdtd|jj}d|D}d|D}t |dkr|gS|r%t jt |dkg}|D]}|d}g|j_|r%|jj |d |jj || ||S) aYThis was used internally for processing search results. Library users probably don't need to care about this one. The logic is now handled directly in the search method. This method is probably used by nobody and nothing, but it can't be removed easily as it's exposed as part of the public API znobj.split_expanded is likely to be removed in a future version of caldav. Feel free to protest if you need it stacklevelcFg|]}t|tj|SrG isinstance icalendarTimezone.0xs rB z9CalendarObjectResource.split_expanded..s*AAAQz!Y-?@@AqAAArDcFg|]}t|tj|SrGrqrus rBrxz9CalendarObjectResource.split_expanded..s*EEEQ:a1C#D#DEqEEErDrT)keep_uidr) warningswarnDeprecationWarningicalendar_instancer<lenr!assert_copyappend)r?rbtz_ntzretical_objobjs rBsplit_expandedz%CalendarObjectResource.split_expandeds  |      # 1AA!AAAEE!EEE s88q==6M  ) M#c((a- ( ( (  H))T)**C35C " 0 D&4;;CFCCC  " 0 7 7 A A A JJsOOOO rDTstartr`include_completedc:tjdtdddl}||jgd||}hdtjtfd |D |j}g|_ |D]}|s#|j d kr| d d vr'tjd |vd |vr.| d | dj||dS)aThis method will transform the calendar content of the event and expand the calendar data from a "master copy" with RRULE set and into a "recurrence set" with RECURRENCE-ID set and no RRULE set. The main usage is for client-side expansion in case the calendar server does not support server-side expansion. If doing a `self.load`, the calendar content will be replaced with the "master copy". :param event: Event :param start: datetime :param end: datetime zlobj.expand_rrule is likely to be removed in a future version of caldav. Feel free to protest if you need itrmrnrN)r8r7r6) components>rdaterruleexdateexrulec3K|]:}t|6|V;dSN) isdisjointsetkeys)rvrwrecurrence_propertiess rB z6CalendarObjectResource.expand_rrule..sMaa!1F1Q1QRUVWV\V\V^V^R_R_1`1`aAaaaaaarDr7STATUS) COMPLETED CANCELLED RECURRENCE-IDrZ)r{r|r}recurring_ical_eventsofr~betweenr!ranyr<r=getrSdt add_component) r?rr`rr recurringscalendar occurrencers @rB expand_rrulez#CalendarObjectResource.expand_rruleso&  z     %$$$*--  #0O0O0O.  '%   !G F F aaaazaaaaa a   *!#$ / /J& Ow..NN8,,0JJJ M/Z7 8 8 8j00 y0I0I0LMMM  " ": . . . . / /rDcP|}t|tr1|jr|j}n@|p |jd}n|}|r|j|}|r%|j|}| ||d|j dd}t|tr|n|g}|D] }||krdS t|}|j d|d|id|dS) zb Sets a relation between this object and another object (given by uid or object). r@F)otherreltype set_reversez related-toNRELTYPET) parametersencode)upperrrr+rCr:rQrKget_object_by_uidr1 set_relationrlistr>rSsave) r?rrrr@reltype_reverseexisting_relationexisting_relationsrels rBrz#CalendarObjectResource.set_relations_--// e3 4 4 ;x Qh**,,P0I%0PC ; 55c::  W#6w?O   T?PU  V V V 488tLL!+,=t!D!D ]  K\J] &  Cczz#hh  $$ #9g*>t %    rDreltypes relfilter fetch_objectsignore_missingcddlm}tt}|jdg}t |ts|g}|D]Z}|r ||s|jdd} |r| |vr2||  t|[|r|D]} || } t} |j tdt |j |std| D]H} | |j | 1#tj$r|sYEwxYw| || <|S) a By default, loads all objects pointed to by the RELATED-TO property and loads the related objects. It's possible to filter, either by passing a set or a list of acceptable relation types in reltypes, or by passing a lambda function in relfilter. TODO: Make it possible to also check up reverse relationships TODO: this is partially overlapped by plann.lib._relships_by_type in the plann tool. Should consolidate the code. TODO: should probably return some kind of object instead of a weird dict structure. (but due to backward compatibility requirement, such an object should behave like the current dict) r)Calendarz RELATED-TOrr-Nz%Unexpected value None for self.parentz9self.parent expected to be of type Calendar but it is not) collectionrrrrQrrrrparamsrSr>rKrhrr! NotFoundError) r?rrrrrr relationsrruids reltype_setrs rB get_relativesz$CalendarObjectResource.get_relativesHs0 )(((((#,00rBB )T** $" I ' 'C 3 jnnY99G G833 L  SXX & & & &  + + +7|!ee ;&$%LMMM!$+x88b$%`aaa""C"# (E(Ec(J(JKKKK ."""-"!""" +G  s-D44E E c|j|}|s!tjd|d|jdS||||dS)NzReltype z not supported in object uid )r1rloggingr!rCr)r?rrreverse_reltypes rB_set_reverse_relationz,CalendarObjectResource._set_reverse_relationse266w??  MMRVRYRYZ [ [ [ F 4%88888rDc|j|}|d|h}|pt|jd}|||vr||fSdS)NF)rrr@)r1rr:r>rQ)r?rr revreltypeother_relationsmy_uids rB_verify_reverse_relationz/CalendarObjectResource._verify_reverse_relationsq-g6 --EZL-YY$$&&N#d.Fu.M*N*N 4 4 4:& &urDverifyfixpdbc>g}|s|sJ|}|D]}}||D]r}|rV|||}|r=|||rt|r|||Z|r|||s~|S)a  Goes through all relations and verifies that the return relation is set if verify is set: Returns a list of objects missing a reverse. Use public method check_reverse_relations instead if verify and fix is set: Fixup all objects missing a reverse. Use public method fix_reverse_relations instead. If fix but not verify is set: Assume all reverse relations are missing. Used internally when creating new objects. )rrr breakpointr) r?rrrrrrrfoobars rB_handle_reverse_relationsz0CalendarObjectResource._handle_reverse_relationss&&((  ? ?G"7+ ? ? ?!::5'JJFG 6***)&LLLG 66ugFFF?..ug>>> ? rDc2|dd|S)a% Will verify that for all the objects we point at though the RELATED-TO property, the other object points back to us as well. Returns a list of tuples. Each tuple contains an object that do not point back as expected, and the expected reltype TFrrrrr?rs rBcheck_reverse_relationsz.CalendarObjectResource.check_reverse_relationss--Tu#-NNNrDc2|dd|S)a& Will ensure that for all the objects we point at though the RELATED-TO property, the other object points back to us as well. Returns a list of tuples. Each tuple contains an object that did not point back as expected, and the expected reltype Trrrs rBfix_reverse_relationsz,CalendarObjectResource.fix_reverse_relationss--Tt-MMMrDc|d|jsdSd|jjD}tjt |dkp| |D]I}t jt jt j t j fD]}t||r|ccSJtjddS)zReturns the icalendar subcomponent - which should be an Event, Journal, Todo or FreeBusy from the icalendar class See also https://github.com/python-caldav/caldav/issues/232 Tonly_if_unloadedNcFg|]}t|tj|SrGrqrus rBrxzCCalendarObjectResource._get_icalendar_component..s;   a!344    rDrF) loadr~r<r!rrrsEventJournalTodoFreeBusyrr)r? assert_onerrwcls rB_get_icalendar_componentz/CalendarObjectResource._get_icalendar_components 4 (((& 4  ,:     c#hh!m5:~666  A!"    a$$HHHHH    erDc|jjfdtdtD}t|dkr||jj|d<dSt j}|d|jd|d|jd||||_dS)NcTg|]$}t|tj"|%SrGrq)rvrbss rBrxzCCalendarObjectResource._set_icalendar_component..s/ U U U1 1Q4AS0T0T UQ U U UrDrrprodidversion)r~r<rangerrsrrSr)r?rErb my_instancers @rB_set_icalendar_componentz/CalendarObjectResource._set_icalendar_components  # 1 U U U UaQ(( U U U q66Q;;:?D # 1!A$ 7 7 7#,..K OOHd&=h&G H H H OOIt'>y'I J J J  % %e , , ,&1D # # #rDaicalendar component - this is the simplest way to access the event/task - it will give you the first component that isn't a timezone component. For recurrence sets, the master component will be returned. For any non-recurring event/task/journal, there should be only one calendar component in the object. For results from an expanded search, there should be only one calendar component in the object)docc|j}d|vr |djSd|vr |djSd|vrd|vr|dj|djzSdS)a A VTODO may have due or duration set. Return or calculate due. WARNING: this method is likely to be deprecated and moved to the icalendar library. If you decide to use it, please put caldav<3.0 in the requirements. DUEDTENDrYrZN)rQrr?rbs rBget_duezCalendarObjectResource.get_duesd  $ A::U8;  \\W:= 1__aYNotImplementedErrorr!rreplaceupdaterQrS) r?rrrr attendee_objrkeynew_keyievents rB add_attendeez#CalendarObjectResource.add_attendeesM( *))))) h * * )#4466LL + . . )#LL % ( ( ){%%i00 D*8A;77 *9x{+BCC (-hqk(:(:L  % % # & & )"":.. A)f$$Y// A*844 S%8%8S=P=P*9x+?@@ M% &==L% <.>qAH ##H--- ##X#666 $*,,>>>    ty ) ) ) ) )    IIKKK   d.00U  C C C[**,,<<>>F|vz))--h-HHHHHH  s3CBF*FFrz new_parentc||p|j|j|r|jnt t j}|s|s||_n |j|_|S)z Events, todos etc can be copied within the same calendar, to another calendar or even to another caldav server )rKrJrC) rVrKrJrCr>uuiduuid1 _generate_urlrI)r?rzr4rs rBrzCalendarObjectResource.copys{ nn,"9twwDJLL(9(9    X ''))CGGhCG rDrcP|r|r|S|jr||S|jt d|jt d |jt|j}|jr,|jdkr!tj t||j |_ n#tj $r|j}|r |cYS#t $rYnwxYw|jrt%|jdr~ |j|}|rK|j|_|j |_ t%|dr|j|j|cYSn#tj $rYnwxYwt $r|cYSwxYwd|jvr$|jd|jt.jj<d |jvr$|jd |jt4jj<|S) a (Re)load the object from the caldav server. For sync clients, loads and returns self. For async clients, returns a coroutine that must be awaited. Example (sync): obj.load() Example (async): await obj.load() rN"Unexpected value None for self.urlrfrrLEtag Schedule-Tag) is_loadedis_async_client _async_loadrIrhrHrequestr>statusr!rr#rawrJrCload_by_multigetr1rKr[rrLr headersr GetEtagtagrr/r?rrr@rs rBrzCalendarObjectResource.loadsi   0 0 K   G##5E#FF F 8 ABB B ; DEE E + ##CMM22Ax 5AHOO)&))444DII"   'C 0022222 D; 74;8K#L#L  "k;;C@@('*wDH(+DI&sG44= $ 1 1#) < < <#'KKK ( !.  + + +((** * * * + QY  *+)F*;DJs{ ' QY & &/0y/HDJt'+ , sb#A+CG (C>;G > D G  D  G +A$FG G F%"G $F%%!G G cLK|r|r|S|jtd|jtd |jt |jd{V}|jr,|jdkr!tjt||j |_ n#tj$r|j }|r | d{VcYS#t$rYnwxYw|jrt!|jdr |j|d{V}|rK|j|_|j |_ t!|dr|j|j|cYSn#tj$rYnwxYwt$r| d{VcYSwxYwd|jvr$|jd|jt*jj<d|jvr$|jd|jt0jj<|S) zAsync implementation of load.Nr:rfr;rrLr<r=)r>rIrhrHrAr>rBr!rr#rCrJrC_async_load_by_multigetr1rKr[rrLr rEr rFrGrr/rHs rBr@z"CalendarObjectResource._async_loads   0 0 K 8 ABB B ; DEE E 8k))#dh--88888888Ax 5AHOO)&))444DII"   'C !%!=!=!?!?????????? D; 74;8K#L#L  $(K$A$A#$F$FFFFFFF('*wDH(+DI&sG44= $ 1 1#) < < <#'KKK ( !.  8 8 85577777777 7 7 7 8 QY  *+)F*;DJs{ ' QY & &/0y/HDJt'+ , sbA1B;;GC0-G0 C=:G<C==GA*F G G FGF'GGc^Ktj|j|j|jgdd{V}|stj|j|d\}|_tj|jtjt|dk|S)z)Async implementation of load_by_multiget.T event_urlsraise_notfoundNrr)r!rrIrK_async_multigetrrJr)r?items_urls rBrKz.CalendarObjectResource._async_load_by_multigets dhk11dhZX\1]]]]]]]] 0%dh// /(di di    c%jjAo&&& rDc`tj|j|j|jgd}t |d}|tj|j|\}|_tj|jtjt |ddu|S)zn Some servers do not accept a GET, but we can still do a REPORT with a multiget query TrMN)r!rrIrK _multigetnextrrJ)r?mydataurl_datarIs rBrDz'CalendarObjectResource.load_by_multigets  dh&&48*T&RR%%   %dh// /!TY di    d64((D0111 rDc|d}|st|ddr|j}|s'|dd}|rt |}|st|ddr|j}|Y|Wt |dr5tjdt | d }| t tj }|dd| d||j jD]M}t|t js1t%j|dd|jkN||}n|jj|}t3j||_dS) a With CalDAV, every object has a URL. With icalendar, every object should have a UID. This UID may or may not be copied into self.id. This method will: 0) if ID is given, assume that as the UID, and set it in the object 1) if UID is given in the object, assume that as the ID 2) if ID is not given, but the path is given, generate the ID from the path 3) If neither ID nor path is given, use the uuid method to generate an ID (TODO: recommendation in the RFC is to concat some timestamp, serial or random number and a domain) 4) if no path is given, generate the URL from the ID F)rrCNr9path.icsz(/|^)([^/]*).icsrm)rgetattrrCrRr>rYendswithresearchgroupr6r7rSr~r<rrrsrtr!rrr8rKrIjoinr' objectify)r?rCrYrbrws rB _find_id_pathz$CalendarObjectResource._find_id_path1s  ) )U ) ; ; gdD$// B ud##B WW fd33 9D :$*s4yy/A/A&/I/I*-s4yy99??BBB :TZ\\""B eT eR(6 = =Aa!344 = aeeE400DG;<<< <%%''DD;?''--D=&&rDcb|j|j|jddi}|jdkrd|jDd}dS|jdvrY|r ddl}n#t$rd}YnwxYw|r|j| dStj t|dS)N Content-Typetext/calendar; charset="utf-8".c6g|]}|ddk|dSrlocationrrGrus rBrxz/CalendarObjectResource._put..b*BBBQqtz/A/AAaD/A/A/ArDrF) rHputrIrJrBrEvobject ImportErrorvobject_instance_putr!PutErrorr#r?retry_on_failurerIrYros rBrrzCalendarObjectResource._put^s KOODHdi.Bb1c d d 8s??BB!)BBB1EDDD XZ ' ' --"NNNN"---',$$$- 0%%yy'''nVAYY///( 'sA A-,A-cK|jt|jt|jddid{V}|jdkr2d|jDd}tj||_dS|jdvr_|r ddl }n#t$rd}YnwxYw|r"|j | dd{VStjt|dS) z(Async version of _put for async clients.rdreNrfc6g|]}|ddk|dSrhrGrus rBrxz5CalendarObjectResource._async_put..yrjrDrrkF)rHrnr>rIrJrBrEr'rarorprq _async_putr!rsr#rts rBrxz!CalendarObjectResource._async_putqs3+// MM  NN = >         8s??BB!)BBB1ED}T**DHHH XZ ' ' --"NNNN"---',$$$- 0%%!__U333333333nVAYY///( 'sB B('B(c\||||dS)NrCrY)rbrr)r?rCrYrus rB_createzCalendarObjectResource._creates, bt,,, rDclK||||d{VdS)z+Async version of _create for async clients.rzN)rbrx)r?rCrYs rB _async_createz$CalendarObjectResource._async_createsG bt,,,oorDc|jjt|jdz}dt |vsJ|S)NrZ )rKrIr`r(rCr>)r?rIs rBr8z$CalendarObjectResource._generate_urlsFko"":dg#6#6#?@@#c(("""" rDrc ddlm}|s/|jtd|j}d}t ||r|}|D]+} |j|fi||dz }#tj $rY(wxYw|s$tj dt|ztj |dkdS|j }|d}t |tr|g}d} |D]9} | | | |kr| j ||dz }:|stj d tj |dkdS) zO Updates the attendee-line according to the arguments received rrNrfrz$Principal %s is not invited to eventrclt|ddS)Nr)r>lowerr )rws rBz?CalendarObjectResource.change_attendee_status..s$Q!7!7 2!F!FrDz)Participant %s not found in attendee list)rrrHrhrirrcalendar_user_address_setr-r!rr>rrQrr ) r?rkwargsrcntattendee_emailsaddrrattendee_lines strip_mailto attendee_lines rBr-z-CalendarObjectResource.change_attendee_statuss *))))) /{" !HIII{,,..H h * * &@@BBO'  /D/?????1HCC*D b)*PSVW_S`S`*`aaa M#( # # # F+!*- nc * * .,-NFF +  M|M**ll8.D.DDD$++F333q S%&QRR R cQhs#A77B B  no_overwrite no_createobj_typeincrease_seqnoif_schedule_tag_matchonly_this_recurrenceall_recurrencescvsSfd}|s|rddlm} sjjjpjd} |} | s|r| j d|r| r| j d|r| s| j d|s|rndjvrddd l ddlm} |} | | j d | j |r| j} j }d D]}|| vr | |||<|j|d jz }|j}|d |d | j|zdD]}||vr|||d|j|z|d jfdt+dt-D}|d}||<|rL|dd D]A}|d }|d |j|zB| |S|rfdt+dt-jD}| jt-|dk|rjj|d<nj| |S|rDdjvr;jdd }|jd|dzjr jjnd }jr|Sj|S)aSave the object, can be used for creation and update. no_overwrite and no_create will check if the object exists. Those two are mutually exclusive. Some servers don't support searching for an object uid without explicitly specifying what kind of object it should be, hence obj_type can be passed. obj_type is only used in conjunction with no_overwrite and no_create. is_schedule_tag_match is currently ignored. (TODO - fix or remove) The SEQUENCE should be increased when saving a new version of the object. If this behaviour is unwanted, then increase_seqno should be set to False. Also, if SEQUENCE is not set, then this will be ignored. The behaviour when saving a single recurrence object to the server is as far as I can understand not defined in the RFCs, but all servers I've tested against will overwrite the full event with the recurrence instance (effectively deleting the recurrence rule). That's almost for sure not what the caller intended. only_this_recurrence and all_recurrences only applies when trying to save a recurrence object. They are by nature mutually exclusive, but since only_this_recurrence is True by default, it will be ignored if all_recurrences is set. If you want to sent the recurrence as it is to the server, you should set both all_recurrences and only_this_recurrence to False. Returns: * self cddlm}jpjd}|rjr sjj}n}|r9d|d}tj|rtj||Stjdrj |Sn#|j $rYdSwxYwdS)Nrr!r@get__by_uidr) caldav.libr!rCrQrrKrV__name__rr[r[rr)r!r@ _obj_type method_namerr?s rBget_selfz-CalendarObjectResource.save..get_selfs ( ( ( ( ( ('@T599%@@C t{   #-$(N$;$A$A$C$C $,  J&?Y&?&?&? "4; <<J#D74; #D#DS#I#IIt{,?@@B#{<.Es?z!A$ HZ7[7[rDrrcrg|]3}j|djdk1|4S)r)r<rrQ)rvrbicir?s rBrxz/CalendarObjectResource.save..Ts\   (+//@@/@AAAAArDSEQUENCErz)r>rr!rVrrrCrQrConsistencyErrorrsrr~rrr\rrcrRrSr<rrrrrrIrYr?_async_save_finalr{)r?rrrrrrrrr!r@existingroccnccprop dtstart_diff new_durationep comp_idxescomp_idxrbrid existing_idxseqnorYrsrrs` ` @@@rBrzCalendarObjectResource.savesZ~~ K      .  b9 b ( ( ( ( ( ( ;>288::'@T599%@@C xzzH X9 X,e,-VWWW e e,e,-cddd b b,e,-`aaa !; ?$3; ?!999     ( ( ( ( ( ((**C{)e)*QRRR(C ?-.3355B..Ds{{$'ID  #y3355O8L8O8Z8Z8\8\\ "|  """ 39|#;<<</$$BSyy \!9:::(((%$QA// &a=!(  I'^IIdhh77!#&<2GHHHHxx~x>>># ?     "1c#*;&<&<==     c,//14555@9=9QC%l1o66%%d&>???xx~x>>>  DjD,DDD,00TBBE (,,ZCCC $2tx}}d   0))$// / d +++ rDcNK||j|d{V|S)z*Async helper for the final save operation.rzN)r}rC)r?rYs rBrz(CalendarObjectResource._async_save_finalps8  DG$ 777777777 rDcZ|sdS|duS)zReturns True if there exists data in the object. An object is considered not to be loaded if it contains no data but just the URL. Optimized to use cheap accessors (issue #613). FN _has_datarPrs rBr>z CalendarObjectResource.is_loadedus2~~ 5--//t;;rDcZ|sdS|duS)a  Returns True if there exists a VEVENT, VTODO or VJOURNAL in the data. Returns False if it's only a VFREEBUSY, VTIMEZONE or unknown components. Used internally after search to remove empty search results (sometimes Google return such) FNrrs rB has_componentz$CalendarObjectResource.has_components2~~ 5--//t;;rDc.|jjd|jS)Nz: )rVrrIrs rB__str__zCalendarObjectResource.__str__s>222DHH==rDcLt|jdr|||St|jdr|||St j||_d|_d|_ |S)Nrors) type __module__r _set_vobject_instance_set_icalendar_instancer"rrT_vobject_instancer;)r?rJs rB _set_dataz CalendarObjectResource._set_datas :: + +I 6 6   & &t , , ,K :: + +K 8 8   ( ( . . .KXd^^ !%#'  rDc|jrt|jS|jr&t|jS|jr&t|jSdSr)rTr$r serializer;to_icalrs rB _get_dataz CalendarObjectResource._get_datast : E ,, ,  # E !7!A!A!C!CDD D  % E !9!A!A!C!CDD DtrDc|jrt|jS|jr&t|jS|jr&t|jSdSr)rTr&rrr;rrs rB_get_wire_dataz%CalendarObjectResource._get_wire_datasq : ?4:&& &  # ?41;;==>> >  % ?43;;==>> >trDz2vCal representation of the object as normal stringz>vCal representation of the object in wire format (UTF-8, CRLN)instvobject.base.ComponentcX||_d|_d|_t||_|Sr)rrTr;rr2r?rs rBrz,CalendarObjectResource._set_vobject_instances-!% #' "4((  rDc ddl}n%#t$rtjdYdSwxYw|js|dS ||t|n5#tdt|j zxYw|jS)NrzA vobject instance has been requested, but the vobject library is not installed (vobject is no longer an official dependency in 2.0)zUSomething went wrong while loading icalendar data into the vobject class. ical url: ) rorprcriticalrrrreadOner%logr>rI)r?ros rB_get_vobject_instancez,CalendarObjectResource._get_vobject_instances  NNNN     W   44   % ~~'t **OOJt~~/?/?$@$@AA  k$(mm$%%s)) AB2Ccbtjdtd|SNz6use event.vobject_instance or event.icalendar_instancermrn)r{r|r}rrs rB _get_deprecated_vobject_instancez7CalendarObjectResource._get_deprecated_vobject_instances8 D     ))+++rDcdtjdtd||Sr)r{r|r}rrs rB _set_deprecated_vobject_instancez7CalendarObjectResource._set_deprecated_vobject_instances: D     ))$///rDzvobject instance of the objectzvobject.base.VBaserqzavobject instance of the object (DEPRECATED! This will yield an icalendar instance in caldav 3.0)instancect|tjs} tj}nF#tj}|dd|ddYnxYw|||}||_d|_d|_t||_ |S)Nrz-//python-caldav//caldav//en_DKrz2.0) rrrsrnewrSrr;rTrrr2)r?rcals rBrz.CalendarObjectResource._set_icalendar_instances$ 233  *(,,.. *(**"CDDD 5)))))   d # # #D#'  !%$T**  s ;AA>c|js?|jsdStjt |j|_|jSr)r;rJrsr from_icalr%r~rs rB_get_icalendar_instancez.CalendarObjectResource._get_icalendar_instancesI' Z9 t&/&8&B&B:diCXCX&Y&YD #''rDz icalendar instance of the objectr~c2|j|jS|jt|j|_nb|jt |j|_nA|j't t|j|_nt|_|jS)zNEnsure we have a DataState object, migrating from legacy attributes if needed.) r2r;rrrrTrr$rrs rB _ensure_statez$CalendarObjectResource._ensure_state$s ; ";   # /()ABBDKK  # /&t'=>>DKK Z #&}TZ'@'@AADKK%--DK{rDcN|S)a5Get raw iCalendar data as string. This is always safe to call and returns the current data without side effects. If the current representation is a parsed object, it will be serialized. Returns: The iCalendar data as a string, or empty string if no data. )rget_datars rBrzCalendarObjectResource.get_data5s"!!##,,...rDcN|S)aGet a COPY of the icalendar object for read-only access. This is safe for inspection - modifications to the returned object will NOT be saved. For editing, use edit_icalendar_instance(). Returns: A copy of the icalendar.Calendar object. )rget_icalendar_copyrs rBget_icalendar_instancez-CalendarObjectResource.get_icalendar_instanceAs"!!##66888rDcN|S)aGet a COPY of the vobject object for read-only access. This is safe for inspection - modifications to the returned object will NOT be saved. For editing, use edit_vobject_instance(). Returns: A copy of the vobject component. )rget_vobject_copyrs rBget_vobject_instancez+CalendarObjectResource.get_vobject_instanceLs"!!##44666rDc#nK|jrtd|}t|ts=|}t ||_d|_d|_||_ d|_ |j Vd|_dS#d|_wxYw)aEContext manager to borrow the icalendar object for editing. Usage:: with event.edit_icalendar_instance() as cal: cal.subcomponents[0]['SUMMARY'] = 'New Summary' event.save() While inside the context, the icalendar object is the authoritative source. Accessing other representations (vobject) while borrowed will raise RuntimeError. Yields: The authoritative icalendar.Calendar object. Raises: RuntimeError: If another representation is currently borrowed. zxCannot borrow icalendar - another representation is already borrowed. Complete the current edit before starting another.NTF) r3 RuntimeErrorrrrrrr2rTrr;get_authoritative_icalendar)r?staters rBedit_icalendar_instancez.CalendarObjectResource.edit_icalendar_instanceWs( > E  ""$$%00 +**,,C(--DKDJ%)D "'*D $ #+99;; ; ; ;"DNNNUDN " " " " B++ B4c#nK|jrtd|}t|ts=|}t ||_d|_d|_||_ d|_ |j Vd|_dS#d|_wxYw)a4Context manager to borrow the vobject object for editing. Usage:: with event.edit_vobject_instance() as vobj: vobj.vevent.summary.value = 'New Summary' event.save() While inside the context, the vobject object is the authoritative source. Accessing other representations (icalendar) while borrowed will raise RuntimeError. Yields: The authoritative vobject component. Raises: RuntimeError: If another representation is currently borrowed. zvCannot borrow vobject - another representation is already borrowed. Complete the current edit before starting another.NTF) r3rrrrrrr2rTr;rget_authoritative_vobject)r?rvobjs rBedit_vobject_instancez,CalendarObjectResource.edit_vobject_instances( > E  ""$$%.. *))++D&t,,DKDJ'+D $%)D " #+7799 9 9 9"DNNNUDN " " " "rcN|S)zGet UID without triggering format conversions. This is for internal use where we just need to peek at the UID without needing to modify anything. )rget_uidrs rBr:z%CalendarObjectResource._get_uid_cheaps" !!##++---rDcN|S)zGet component type (VEVENT/VTODO/VJOURNAL) without parsing. This is for internal use to quickly determine the type. )rget_component_typers rBrPz0CalendarObjectResource._get_component_type_cheaps" !!##66888rDcN|S)z9Check if we have any data without triggering conversions.)rhas_datars rBrz CalendarObjectResource._has_datas !!##,,...rDc:|j}||S)a*According to the RFC, either DURATION or DUE should be set for a task, but never both - implicitly meaning that DURATION is the difference between DTSTART and DUE (personally I believe that's stupid. If a task takes five minutes to complete - say, fill in some simple form that should be delivered before midnight at new years eve, then it feels natural for me to define "duration" as five minutes, DTSTART to "some days before new years eve" and DUE to 20xx-01-01 00:00:00 - but I digress. This method will return DURATION if set, otherwise the difference between DUE and DTSTART (if both of them are set). TODO: should be fixed for Event class as well (only difference is that DTEND is used rather than DUE) and possibly also for Journal (defaults to one day, probably?) WARNING: this method is likely to be deprecated and moved to the icalendar library. If you decide to use it, please put caldav<3.0 in the requirements. )rQ _get_durationrs rBr^z#CalendarObjectResource.get_durations ,  $!!!$$$rDcd|vr |djSd|vr|j|vr||jj}|dj}t|tt|tkr@t|j|j|j}t|j|j|j}||z Sd|vr+t|dtstdStdS)NrYrZr)daysr)rr_rrryearmonthdayr)r?rbr`rs rBrz$CalendarObjectResource._get_durations ??Z=# # !^^! 3 3DN#&CiLOE#x((Juh,G,GGG U[%)DDsxCG<<;  !^^Jq|X$F$F^!$$$ $Q<< rD)NNNNNN)Fr4N)T)NT)NNTT)FFFr)FNNN)NNT)FFNTFTF)rr)r4r)hrr __qualname____doc__r1r__annotations__r_rr;rTr2rr3boolpropertyr>rCsetterr r r r'rrOrdrkrrrrrrrrrrrrr rrrrrrrQ componentr get_dtendrrrr!r%r(rrrr@rKrDrbrrrxr{r}r8r-rrr>rrrrrrJ wire_datarrrrrqrrrr~rrrsrrrrrrr:rPrrr^r __classcell__)rVs@rBr+r+=s   *%$ % %   I E $FI ###It C$JX"Y d  t   Y )-<@! GG%G;  ,s 2T 9GDj G d G $J GTzG GGGGGG2####. P P P P T    D4/4/(4/4/d4/^b4/4/4/4/n04* ****b+/26"# ::C.4':SE4K(4/: :  : S#c(] # ::::x999 %    DI)-<@ @ O O4 ODK O O O O N N N$ N N N N6 2 2 2 2#(   a $I$I?-?-D?-[_?-?-?-?-BH4HHHHFFFFF<>>>>$9"VD# LI &x0H'I&&&&2,(;S2T,,,,0000.6X ,...* &.X(( o&&&H" (((('h .y" /# / / / / 9 (: 9 9 9 9 7 7 7 7(#(#^(#T(#(#^(#X.d ....93:9999/4////%i%%%%2       rDr+c$eZdZdZejZdZdS)rz The `Event` object is used to represent an event (VEVENT). As of 2020-12 it adds very little to the inheritated class. (I have frequently asked myself if we need those subclasses ... perhaps not) rN)rrrrr+rd set_dtendr_rGrDrBrrs''.IIIIrDrceZdZdZdS)rz The `Journal` object is used to represent a journal entry (VJOURNAL). As of 2020-12 it adds nothing to the inheritated class. (I have frequently asked myself if we need those subclasses ... perhaps not) N)rrrrrGrDrBrrs DrDrcJeZdZdZ ddeezezezdzdedzddfdZ dS)ra The `FreeBusy` object is used to represent a freebusy response from the server. __init__ is overridden, as a FreeBusy response has no URL or ID. The inheritated methods .save and .load is moot and will probably throw errors (perhaps the class hierarchy should be rethought, to prevent the FreeBusy from inheritating moot methods) Update: With RFC6638 a freebusy object can have a URL and an ID. NrIrCr4cPt||j||||dS)N)rHrIrJrKrC)r+rOrH)r?rKrJrIrCs rBrOzFreeBusy.__init__s: '' Cd6b (     rDr) rrrrr>r r r'rrOrGrDrBrr sv=A   ;  ,s 2T 9  $J         rDrc eZdZdZdZddZddefdZdZdd Z dd e dzd ede dddfdZ dddZ ddedzfdZddZddZdddZddZeZdS)raThe `Todo` object is used to represent a todo item (VTODO). A Todo-object can be completed. There is some extra logic here - arguably none of it belongs to the caldav library, and should be moved either to the icalendar library or to the plann library (plann is a cli-tool, should probably be split up into one library for advanced calendaring operations and the cli-tool as separate packages) rNTcj|s|j}|s|d}|sr|dus|Atd|Dr(d|vr|dj}nA|ptj}n+|p(tj||z }t |dr|tj }|s|}|r-d|vr)| }| dt| d| }||S) abSpecial logic to fint the next DTSTART of a recurring just-completed task. If any BY*-parameters are present, assume the task should have fixed deadlines and preserve information from the previous dtstart. If no BY*-parameters are present, assume the frequency is meant to be the interval between the tasks. Examples: 1) Garbage collection happens every week on a Tuesday, but never earlier than 09 in the morning. Hence, it may be important to take out the thrash Monday evenings or Tuesday morning. DTSTART of the original task is set to Tuesday 2022-11-01T08:50, DUE to 09:00. 1A) Task is completed 07:50 on the 1st of November. Next DTSTART should be Tuesday the 7th of November at 08:50. 1B) Task is completed 09:15 on the 1st of November (which is probably OK, since they usually don't come before 09:30). Next DTSTART should be Tuesday the 7th of November at 08:50. 1C) Task is completed at the 5th of November. We've lost the DUE, but the calendar has no idea weather the DUE was a very hard due or not - and anyway, probably we'd like to do it again on Tuesday, so next DTSTART should be Tuesday the 7th of November at 08:50. 1D) Task is completed at the 7th of November at 07:50. Next DTSTART should be one hour later. Now, this is very silly, but an algorithm cannot do guesswork on weather it's silly or not. If DTSTART would be set to the earliest possible time one could start thinking on this task (like, Monday evening), then we would get Tue the 14th of November, which does make sense. Unfortunately the icalendar standard does not specify what should be used for DTSTART and DURATION/DUE. 1E) Task is completed on the 7th of November at 08:55. This efficiently means we've lost the 1st of November recurrence but have done the 7th of November recurrence instead, so next timestamp will be the 14th of November. 2) Floors at home should be cleaned like once a week, but there is no fixed deadline for it. For some people it may make sense to have a routine doing it i.e. every Tuesday, but this is not a strict requirement. If it wasn't done one Tuesday, it's probably even more important to do it Wednesday. If the floor was cleaned on a Saturday, it probably doesn't make sense cleaning it again on Tuesday, but it probably shouldn't wait until next Tuesday. Rrule is set to FREQ=WEEKLY, but without any BYDAY. The original VTODO is set up with DTSTART 16:00 on Tuesday the 1st of November and DUE 17:00. After 17:00 there will be dinner, so best to get it done before that. 2A) Floor cleaning was finished 14:30. The next recurrence has DTSTART set to 13:30 (and DUE set to 14:30). The idea here is that since the floor starts accumulating dirt right after 14:30, obviously it is overdue at 16:00 Tuesday the 7th. 2B) Floor cleaning was procrastinated with one day and finished Wednesday at 14:30. Next instance will be Wednesday in a week, at 14:30. 2C) Floor cleaning was procrastinated with two weeks and finished Tuesday the 14th at 14:30. Next instance will be Tuesday the 21st at 14:30. While scenario 2 is the most trivial to implement, it may not be the correct understanding of the RFC, and it may be tricky to get the RECURRENCE-ID set correctly. RRULETNc3DK|]}|d|VdS)BYN)r rus rBrzTodo._next..s40X0XqQ\\RVEWEW0X0X0X0X0X0X0XrDrZr\COUNTzutf-8)r)rQrrrnowrr[r\rr]rrRr rdecodeafter)r?tsrbrrbyno_counts rB_nextz Todo._next/sAV )(A gJE GTzzbjS0X0XE0X0X0X-X-Xj>> loGG 2HLNNGGF 1C1CA1F1F F 7L ) ) 7((66G B  5((JJLLE IIg   //88'JJJ{{2rDr4c|s|j}d|dvr6|ddddkrdS|dddxxdzcc<dS)NrrrrFT)rQrs rB _reduce_countzTodo._reduce_countsi )(A aj z'"1%**u gJw  " " "a ' " " "trDc|s|dS||}|s|dS|}|jj|jdz|_|j d| || }|j}| dd| d|| |d| dS) aDThis mode will create a new independent task which is marked as completed, and modify the existing recurring task. It is probably the most safe way to handle the completion of a recurrence of a recurring task, though the link between the completed task and the original task is lost. F) handle_rrulerZrrZNr) movable_attr)rcompleterrrKrIr`rCrQrRrr^rS set_duration)r?completion_timestamp next_dtstart completedrcrbs rB_complete_recurring_safezTodo._complete_recurring_safes+!!## 5==e=44 4zz"677  5==e=44 4IIKK  ,,Y\F-BCC %))'222$$&&  $ i i&&& (777 rDcBjj}|d}d|vrd|d<t|dkr|}|d|d|d||dd}|d|dz|||d }|d|d}|}|dd}|d|dzt|d krU|djd d d kr!|djd ntd |||dd |d ||d |djd <|dd } | U| dd } | &| ddvr|D]} | ||d| nr|dd } | Z| dtfd|Dkr5 |d| dd S| p|} |} |dd |dd  |||} |d| || djj| dd S)aThe RFC is not much helpful, a lot of guesswork is needed to consider what the "right thing" to do wrg of a completion of recurring tasks is ... but this is my shot at it. 1) The original, with rrule, will be kept as it is. The rrule string is fetched from the first subcomponent of the icalendar. 2) If there are multiple recurrence instances in subcomponents and the last one is marked with RANGE=THISANDFUTURE, then select this one. If it has the rrule property set, use this rrule rather than the original one. Drop the RANGE parameter. Calculate the next RECURRENCE-ID from the DTSTART of this object. Mark task as completed. Increase SEQUENCE. 3) Create a new recurrence instance with RANGE=THISANDFUTURE, without RRULE set (Ref https://github.com/Kozea/Radicale/issues/1264). Set the RECURRENCE-ID to the one calculated in #2. Calculate the DTSTART based on rrule and completion timestamp/date. rrrrrrrZrrmRANGEN THISANDFUTUREzmultiple instances found, but last one is not of type THISANDFUTURE, possibly this has been created by some incompatible client, but we should deal with it)rbrr)rrr$c>g|]}||SrG) is_pending)rvrwr?s rBrxz:Todo._complete_recurring_thisandfuture..s*BBBqtq/A/ABBBBrDFr)rbr)rbrr)rbrcr!)r~r<rrrRrSrrrr _complete_icalrrr _set_duration)r?r$ recurrencesorigjust_completedrprevr thisandfuturerrule2countrbrcr%s` rB!_complete_recurring_thisandfuturez&Todo._complete_recurring_thisandfutures,-; 1~ 4  +DN {  q !YY[[N   w ' ' '   DX0Y0Y Z Z Z"&&z155E   z519 5 5 5   ~ . . .2$w-00 !!*a00*eai000 {  a  O$+//>>/QQ_%,009999)r D"6777/4000/4::E:+J+JKKK9H o&-g6""7D11  JJw--E U1X%7%7$VVA''@T'UUUU   gv . . . .IIgt,,E U1XBBBBKBBB22&&##KNI]#^^^  ///%%%%--)T***%&&&zzD:NzOO )\222 ]XERRR -44]CCC  '''''rDFsafer$r  rrule_mode)r9this_and_futurec|stjtj}d|jvr|rt |d|z|S|||dS)aMarks the task as completed. Parameters ---------- completion_timestamp : datetime Defaults to ``datetime.now()``. handle_rrule : Bool If set to True, the library will try to be smart if the task is recurring. The default is False, for backward compatibility. I may consider making this one mandatory. rrule_mode : str The RFC leaves a lot of room for interpretation on how to handle recurring tasks, and what works on one server may break at another. The following modes are accepted: * this_and_future - see doc for _complete_recurring_thisandfuture for details * safe - see doc for _complete_recurring_safe for details rz_complete_recurring_%sr,N)rrrr]rQr[r/r)r?r$r r:s rBr"z Todo.completes{.$ >#+< #=#= d. . .< .G74!9J!FGGH\]] ] 1EFFF rDc||j}||sJ|dd}|dd|d|dS)Nrr)rQr.rRrS)r?rbr$rBs rBr/zTodo._complete_ical0si 9(Aq!!!!!x&& h $$$ k/00000rDc||j}|dddS|dddvrdS|dddvrdSJ)NrFrr)rz IN-PROCESST)rr)rQrrs rBr.zTodo.is_pending8sk 9(A 55d # # /5 55> * *.L L L4 55> * *.H H H5 rDcd|jvr|jd|jddd|jvr|jd|dS)z9Undo completion - marks a completed task as not completedrBrr&N)rQrRrSrrs rB uncompletezTodo.uncompleteDsx t/ / /  $ ( ( 2 2 2  $$X~>>> $2 2 2  $ ( ( 5 5 5 rDrZc>|j}||||S)a If DTSTART and DUE/DTEND is already set, one of them should be moved. Which one? I believe that for EVENTS, the DTSTART should remain constant and DTEND should be moved, but for a task, I think the due date may be a hard deadline, hence by default we'll move DTSTART. TODO: can this be written in a better/shorter way? WARNING: this method may be deprecated and moved to the icalendar library at some point in the future. )rQr0)r?rcr!rbs rBr#zTodo.set_durationPs$  $!!!X|<<11111  D4K         = = = =((((($ @ @ @ @DGGGrDr)Drrr]sysr6r{ collectionsrrrrtypingrrr urllib.parser r rsdateutil.rruler r rrdate TimeStamp davclientrcollections.abcrrr version_infotyping_extensionsr contextlibr datastaterrrrr davobjectrelementsrr libr!r" lib.errorr#lib.python_utilitiesr$r%r&lib.urlr'operations.calendarobject_opsr( getLoggerrr+rrrrrGrDrBr_sw   ######2222222222//////////11111111######(((((((( )))))))))II D%%%%%%%$$$$$$////////g&&&&&&&%%%%%%YYYYYYYYYYYYYY DDDDDDDDDD555555g!!r r r r r Yr r r j-      "         $         %   .nnnnn !nnnnns A A$