U j@sdZddlmZddlZddlZddlZddlmZmZmZm Z ddl m Z ddl m Z ddlmZddlmZmZmZdd lmZmZmZmZmZd d lmZmZmZed Zed Z GdddZ!Gddde"Z#Gddde$Z%Gddde$Z&Gddde'Z(Gddde"Z)GdddZ*GdddZ+GdddZ,Gd d!d!e,Z-Gd"d#d#e,Z.Gd$d%d%e,Z/Gd&d'd'e,Z0Gd(d)d)e,Z1Gd*d+d+e$Z2Gd,d-d-e$Z3Gd.d/d/e"Z4Gd0d1d1e%eZ5Gd2d3d3e Z6Gd4d5d5e,Z7Gd6d7d7e$Z8Gd8d9d9Z9Gd:d;d;Z:Gdd?d?e Z[+-]?)(?P[\d]{0,2})(?P[\w]{2})$c@sFeZdZUdZded<ddZddZdd Zed d Z d d Z dS)vBinaryz+Binary property values are base 64 encoded.r paramscCst||_tddd|_dS)NBASE64ZBINARY)encodingvalue)robjr r)selfrr2/tmp/pip-unpacked-wheel-g40nyxg1/icalendar/prop.py__init__Ps zvBinary.__init__cCsd|dS)NzvBinary()to_icalrrrr__repr__TszvBinary.__repr__cCst|jdddS)Nutf-8)binascii b2a_base64rencoder#rrrr"WszvBinary.to_icalc Cs2z t|WSttfk r,tdYnXdS)NzNot valid base 64 encoding.)base64 b64decode ValueError UnicodeErroricalrrr from_icalZs zvBinary.from_icalcCst|to|j|jkS self == other) isinstancerrrotherrrr__eq__aszvBinary.__eq__N) __name__ __module__ __qualname____doc____annotations__rr$r" staticmethodr0r6rrrrrKs  rcsReZdZUdZded<edddZidfdd Zd d Ze d d Z Z S)vBooleanaBoolean Value Name: BOOLEAN Purpose: This value type is used to identify properties that contain either a "TRUE" or "FALSE" Boolean value. Format Definition: This value type is defined by the following notation: .. code-block:: text boolean = "TRUE" / "FALSE" Description: These values are case-insensitive text. No additional content value encoding is defined for this value type. Example: The following is an example of a hypothetical property that has a BOOLEAN value type: .. code-block:: python TRUE .. code-block:: pycon >>> from icalendar.prop import vBoolean >>> boolean = vBoolean.from_ical('TRUE') >>> boolean True >>> boolean = vBoolean.from_ical('FALSE') >>> boolean False >>> boolean = vBoolean.from_ical('True') >>> boolean True r rTF)truefalsercs"tj|f||}t||_|SNsuper__new__r rclsrargskwargsr __class__rrrDs zvBoolean.__new__cCs |rdSdS)NsTRUEsFALSErr#rrrr"szvBoolean.to_icalcCs4z |j|WStk r.td|YnXdS)Nz Expected 'TRUE' or 'FALSE'. Got )BOOL_MAP Exceptionr,rFr/rrrr0s zvBoolean.from_ical) r7r8r9r:r;rrKrDr" classmethodr0 __classcell__rrrIrr=fs &r=csreZdZUdZded<eiffdd Zdddd Zd dd d Ze d dddZ ddl m Z m Z mZZS)vTextz Simple text.r rcs.t||d}t||}||_t||_|SNr)rrCrDrr rrFrrrrrIrrrDs   z vText.__new__strreturncCsd|dS)NzvText(r r!r#rrrr$szvText.__repr__bytescCst||jSrA)r r)rr#rrrr"sz vText.to_icalrr.cCst|}||SrA)r )rFr/Z ical_unescrrrr0szvText.from_icalr)ALTREPLANGUAGERELTYPE)r7r8r9r:r;r rDr$r"rNr0icalendar.paramrXrYrZrOrrrIrrPs rPcseZdZUdZded<eiffdd ZddZdd Ze d d Z e d d ddZ ddl mZmZmZmZmZmZmZmZmZmZeZZS) vCalAddressaCalendar User Address Value Name: CAL-ADDRESS Purpose: This value type is used to identify properties that contain a calendar user address. Description: The value is a URI as defined by [RFC3986] or any other IANA-registered form for a URI. When used to address an Internet email transport address for a calendar user, the value MUST be a mailto URI, as defined by [RFC2368]. Example: ``mailto:`` is in front of the address. .. code-block:: text mailto:jane_doe@example.com Parsing: .. code-block:: pycon >>> from icalendar import vCalAddress >>> cal_address = vCalAddress.from_ical('mailto:jane_doe@example.com') >>> cal_address vCalAddress('mailto:jane_doe@example.com') Encoding: .. code-block:: pycon >>> from icalendar import vCalAddress, Event >>> event = Event() >>> jane = vCalAddress("mailto:jane_doe@example.com") >>> jane.name = "Jane" >>> event["organizer"] = jane >>> print(event.to_ical()) BEGIN:VEVENT ORGANIZER;CN=Jane:mailto:jane_doe@example.com END:VEVENT r rcs(t||d}t||}t||_|SrQrrCrDr rrSrIrrrDs  zvCalAddress.__new__cCs d|dS)Nz vCalAddress('z')rr#rrrr$szvCalAddress.__repr__cCs |tSrAr)r r#rrrr"szvCalAddress.to_icalcCs||SrArrMrrrr0szvCalAddress.from_icalrTrUcCs"|dr|ddSt|S)z/The email address without mailto: at the start.zmailto:N)lower startswithrTr#rrremails zvCalAddress.emailr) CNCUTYPEDELEGATED_FROM DELEGATED_TODIRrYPARTSTATROLERSVPSENT_BY)r7r8r9r:r;r rDr$r"rNr0propertyrbr[rcrdrerfrgrYrhrirjrknamerOrrrIrr\s . 0 r\csDeZdZUdZded<idfdd ZddZed d ZZ S) vFloataFloat Value Name: FLOAT Purpose: This value type is used to identify properties that contain a real-number value. Format Definition: This value type is defined by the following notation: .. code-block:: text float = (["+"] / "-") 1*DIGIT ["." 1*DIGIT] Description: If the property permits, multiple "float" values are specified by a COMMA-separated list of values. Example: .. code-block:: text 1000000.0000001 1.333 -3.14 .. code-block:: pycon >>> from icalendar.prop import vFloat >>> float = vFloat.from_ical('1000000.0000001') >>> float 1000000.0000001 >>> float = vFloat.from_ical('1.333') >>> float 1.333 >>> float = vFloat.from_ical('+1.333') >>> float 1.333 >>> float = vFloat.from_ical('-3.14') >>> float -3.14 r rr@cs"tj|f||}t||_|SrArBrErIrrrDCs zvFloat.__new__cCst|dSNr%rTr)r#rrrr"HszvFloat.to_icalcCs2z ||WStk r,td|YnXdS)NzExpected float value, got: rLr,rMrrrr0Ks zvFloat.from_ical r7r8r9r:r;rDr"rNr0rOrrrIrrns -rncsPeZdZUdZded<idfdd Zddd d Zed d d dZZ S)vIntaInteger Value Name: INTEGER Purpose: This value type is used to identify properties that contain a signed integer value. Format Definition: This value type is defined by the following notation: .. code-block:: text integer = (["+"] / "-") 1*DIGIT Description: If the property permits, multiple "integer" values are specified by a COMMA-separated list of values. The valid range for "integer" is -2147483648 to 2147483647. If the sign is not specified, then the value is assumed to be positive. Example: .. code-block:: text 1234567890 -1234567890 +1234567890 432109876 .. code-block:: pycon >>> from icalendar.prop import vInt >>> integer = vInt.from_ical('1234567890') >>> integer 1234567890 >>> integer = vInt.from_ical('-1234567890') >>> integer -1234567890 >>> integer = vInt.from_ical('+1234567890') >>> integer 1234567890 >>> integer = vInt.from_ical('432109876') >>> integer 432109876 r rr@cs"tj|f||}t||_|SrArBrErIrrrDs z vInt.__new__rWrUcCst|dSrorpr#rrrr"sz vInt.to_icalrr.cCs2z ||WStk r,td|YnXdS)NzExpected int, got: rqrMrrrr0s zvInt.from_icalrrrrrIrrsSs 0rsc@sPeZdZUdZded<ded<ddZdd Zedd d Zd dZ ddZ d S) vDDDListszA list of vDDDTypes values.r rlistdtscCslt|ds|g}g}d}|D]*}t|}||d|jkr|jd}qi}|rX||d<t||_||_dS)N__iter__TZID)hasattr vDDDTypesappendrr rv)rZdt_listZvDDDtziddtrrrrrs     zvDDDLists.__init__cCsdd|jD}d|S)Ncss|]}t|VqdSrA)rr").0r}rrr sz$vDDDLists.to_ical..,)rvjoin)rZdts_icalrrrr"szvDDDLists.to_icalNcCs0g}|d}|D]}|tj||dq|S)N,timezone)splitr{rzr0)r/routZ ical_datesZical_dtrrrr0s  zvDDDLists.from_icalcCs4t|tr|j|jkSt|ttfr0|j|gkSdSNF)r3rtrvTimeBaserr4rrrr6s    zvDDDLists.__eq__cCs|jjd|jdS)String representation.(r )rJr7rvr#rrrr$szvDDDLists.__repr__)N r7r8r9r:r;rr"r<r0r6r$rrrrrts  rtc@sLeZdZUded<ifddddZddZd d Zed d Zd dZ dS) vCategoryr rzlist[str] | str)c_listcCs8t|drt|tr|g}dd|D|_t||_dS)NrwcSsg|] }t|qSr)rPr~crrr sz&vCategory.__init__..)ryr3rTcatsr r)rrrrrrrszvCategory.__init__cCstt|SrA)iterrr0r"r#rrrrwszvCategory.__iter__cCsddd|jDS)NrcSs*g|]"}t|dr|n t|qSr!)ryr"rPrrrrrsz%vCategory.to_ical..)rrr#rrrr"s zvCategory.to_icalcCst|}t|d}|S)Nr)rr r)r/rrrrr0szvCategory.from_icalcCst|to|j|jkSr1)r3rrr4rrrr6szvCategory.__eq__N) r7r8r9r;rrwr"r<r0r6rrrrrs  rc@sNeZdZUdZded<ddhZddZdd Zd d lm Z m Z m Z d d Z dS)rz-Make classes with a datetime/date comparable.r rrxZVALUEcCst|tr|j|kSt|trt}t|jt|jB|jD]:}|dddkr>|j |||j ||kr>dSq>|j|jkSt|t r||kSdS)r2Nzx-F) r3rr}robjectsetrignore_for_equalityr`getrt)rr5defaultkeyrrrr6s$      zTimeBase.__eq__cCs t|jSrA)hashr}r#rrr__hash__szTimeBase.__hash__r)RANGERELATEDrxcCs|jjd|jd|jdS)rr, r )rJr7r}rr#rrrr$szTimeBase.__repr__N) r7r8r9r:r;rr6rr[rrrxr$rrrrrs rc@s8eZdZUdZded<ddZddZed d d ZdS) rzzA combined Datetime, Date or Duration parser/generator. Their format cannot be confused, and often values can be of either types. So this is practical. r rcCst|tttttfstdt|ttfr4t|_nBt|trNtddi|_n(t|trhtddi|_ntddi|_t|ttfrt |nd}|dk r|dkr|j d|i||_ dS)NzCYou must use datetime, date, timedelta, time or tuple (for periods)rDATETIMEPERIODUTCrx) r3rrrrtupler,r rrupdater})rr}r|rrrrs   zvDDDTypes.__init__cCs|j}t|trt|St|tr2t|St|trHt|St|t r^t |St|t rt |dkrt |Stdt|dS)NrzUnknown date type: )r}r3r vDatetimer"rvDater vDurationrvTimerlenvPeriodr,typerr}rrrr"#s         zvDDDTypes.to_icalNcCst||r|jS|}|dr,t|Sd|krBtj||dSt|dkr\tj||dSt|dkrrt |St|dkrt |St d|ddS) N)Pz-Pz+P/r))r_z(Expected datetime, date, or time, got: '') r3r}upperrarr0rrrrrr,)rFr/rurrrr02s        zvDDDTypes.from_ical)N) r7r8r9r:r;rr"rNr0rrrrrzs rzc@s6eZdZUdZded<ddZddZedd Zd S) raDate Value Name: DATE Purpose: This value type is used to identify values that contain a calendar date. Format Definition: This value type is defined by the following notation: .. code-block:: text date = date-value date-value = date-fullyear date-month date-mday date-fullyear = 4DIGIT date-month = 2DIGIT ;01-12 date-mday = 2DIGIT ;01-28, 01-29, 01-30, 01-31 ;based on month/year Description: If the property permits, multiple "date" values are specified as a COMMA-separated list of values. The format for the value type is based on the [ISO.8601.2004] complete representation, basic format for a calendar date. The textual format specifies a four-digit year, two-digit month, and two-digit day of the month. There are no separator characters between the year, month, and day component text. Example: The following represents July 14, 1997: .. code-block:: text 19970714 .. code-block:: pycon >>> from icalendar.prop import vDate >>> date = vDate.from_ical('19970714') >>> date.year 1997 >>> date.month 7 >>> date.day 14 r rcCs*t|tstd||_tddi|_dS)NzValue MUST be a date instancerr)r3rr,r}r rrrrrr{s zvDate.__init__cCs,|jjd|jjd|jjd}|dS)N0402r%)r}yearmonthdayr))rsrrrr"s"z vDate.to_icalcCs`z8t|ddt|ddt|ddf}t|WStk rZtd|YnXdS)NrrzWrong date format )intrrLr,r/ timetuplerrrr0s zvDate.from_icalN r7r8r9r:r;rr"r<r0rrrrrFs 2rc@s<eZdZUdZded<ifddZddZed d d ZdS) raRender and generates icalendar datetime format. vDatetime is timezone aware and uses a timezone library. When a vDatetime object is created from an ical string, you can pass a valid timezone identifier. When a vDatetime object is created from a python datetime object, it uses the tzinfo component, if present. Otherwise a timezone-naive object is created. Be aware that there are certain limitations with timezone naive DATE-TIME components in the icalendar standard. r rcCs||_t||_dSrA)r}r r)rr}rrrrrszvDatetime.__init__cCst|j}t|}|jd|jd|jdd|jd|jd|jd}|dkrV|d7}n|rj|j d|i| dS)NrrTrZrxr%) r}rrrrhourminutesecondrrr))rr}r|rrrrr"s6 zvDatetime.to_icalNc Csd}t|trt|}n |dk r&|}zt|ddt|ddt|ddt|ddt|ddt|ddf}|rtt||WS|ddst|WS|dd d krtt|WSt|Wn4t k r }ztd ||W5d}~XYnXdS) aCreate a datetime from the RFC string. Format: .. code-block:: text YYYYMMDDTHHMMSS .. code-block:: pycon >>> from icalendar import vDatetime >>> vDatetime.from_ical("20210302T101500") datetime.datetime(2021, 3, 2, 10, 15) >>> vDatetime.from_ical("20210302T101500", "America/New_York") datetime.datetime(2021, 3, 2, 10, 15, tzinfo=ZoneInfo(key='America/New_York')) >>> from zoneinfo import ZoneInfo >>> timezone = ZoneInfo("Europe/Berlin") >>> vDatetime.from_ical("20210302T101500", timezone) datetime.datetime(2021, 3, 2, 10, 15, tzinfo=ZoneInfo(key='Europe/Berlin')) Nrrr rrrzWrong datetime format: ) r3rTrrrZlocalizerZ localize_utcr,rL)r/rtzinforerrrr0s,     zvDatetime.from_ical)Nrrrrrrs    rc@sLeZdZUdZded<ifddZddZedd Ze d d d d Z dS)ra Duration Value Name: DURATION Purpose: This value type is used to identify properties that contain a duration of time. Format Definition: This value type is defined by the following notation: .. code-block:: text dur-value = (["+"] / "-") "P" (dur-date / dur-time / dur-week) dur-date = dur-day [dur-time] dur-time = "T" (dur-hour / dur-minute / dur-second) dur-week = 1*DIGIT "W" dur-hour = 1*DIGIT "H" [dur-minute] dur-minute = 1*DIGIT "M" [dur-second] dur-second = 1*DIGIT "S" dur-day = 1*DIGIT "D" Description: If the property permits, multiple "duration" values are specified by a COMMA-separated list of values. The format is based on the [ISO.8601.2004] complete representation basic format with designators for the duration of time. The format can represent nominal durations (weeks and days) and accurate durations (hours, minutes, and seconds). Note that unlike [ISO.8601.2004], this value type doesn't support the "Y" and "M" designators to specify durations in terms of years and months. The duration of a week or a day depends on its position in the calendar. In the case of discontinuities in the time scale, such as the change from standard time to daylight time and back, the computation of the exact duration requires the subtraction or addition of the change of duration of the discontinuity. Leap seconds MUST NOT be considered when computing an exact duration. When computing an exact duration, the greatest order time components MUST be added first, that is, the number of days MUST be added first, followed by the number of hours, number of minutes, and number of seconds. Example: A duration of 15 days, 5 hours, and 20 seconds would be: .. code-block:: text P15DT5H0M20S A duration of 7 weeks would be: .. code-block:: text P7W .. code-block:: pycon >>> from icalendar.prop import vDuration >>> duration = vDuration.from_ical('P15DT5H0M20S') >>> duration datetime.timedelta(days=15, seconds=18020) >>> duration = vDuration.from_ical('P7W') >>> duration datetime.timedelta(days=49) r rcCs&t|tstd||_t||_dS)Nz"Value MUST be a timedelta instancer3rr,tdr rrrrrrrr)s zvDuration.__init__cCsd}|j}|jdkrd}| }d}|jrd}|jd}|jdd}|jd}|r`||d7}|sl|rz|rz||d7}|r||d 7}|jdkr|rt|d d t|d St|d d tt|jd d t|d SdS) Nr-r<HMSr%PD)rdayssecondsrTr)abs)rsignrZtimeparthoursminutesrrrrr"/s:       zvDuration.to_icalc Cs|t|}|std||\}}}}}}tt|p:dt|pDdt|pNdt|pXdt|pbdd}|dkrx| }|S)NzInvalid iCalendar duration: r)weeksrrrrr)DURATION_REGEXmatchr,groupsrr) r/rrrrrrrrrrrr0Ls      zvDuration.from_icalrrUcCs|jS)z!The time delta for compatibility.rr#rrrr}`sz vDuration.dtN) r7r8r9r:r;rr"r<r0rlr}rrrrrs D  rc@sfeZdZUdZded<ddddZdd Zd d Zedd dZ ddZ e ddZ ddl mZd S)ra" Period of Time Value Name: PERIOD Purpose: This value type is used to identify values that contain a precise period of time. Format Definition: This value type is defined by the following notation: .. code-block:: text period = period-explicit / period-start period-explicit = date-time "/" date-time ; [ISO.8601.2004] complete representation basic format for a ; period of time consisting of a start and end. The start MUST ; be before the end. period-start = date-time "/" dur-value ; [ISO.8601.2004] complete representation basic format for a ; period of time consisting of a start and positive duration ; of time. Description: If the property permits, multiple "period" values are specified by a COMMA-separated list of values. There are two forms of a period of time. First, a period of time is identified by its start and its end. This format is based on the [ISO.8601.2004] complete representation, basic format for "DATE- TIME" start of the period, followed by a SOLIDUS character followed by the "DATE-TIME" of the end of the period. The start of the period MUST be before the end of the period. Second, a period of time can also be defined by a start and a positive duration of time. The format is based on the [ISO.8601.2004] complete representation, basic format for the "DATE-TIME" start of the period, followed by a SOLIDUS character, followed by the [ISO.8601.2004] basic format for "DURATION" of the period. Example: The period starting at 18:00:00 UTC, on January 1, 1997 and ending at 07:00:00 UTC on January 2, 1997 would be: .. code-block:: text 19970101T180000Z/19970102T070000Z The period start at 18:00:00 on January 1, 1997 and lasting 5 hours and 30 minutes would be: .. code-block:: text 19970101T180000Z/PT5H30M .. code-block:: pycon >>> from icalendar.prop import vPeriod >>> period = vPeriod.from_ical('19970101T180000Z/19970102T070000Z') >>> period = vPeriod.from_ical('19970101T180000Z/PT5H30M') r rz+tuple[datetime, Union[datetime, timedelta]])percCs|\}}t|ts$t|ts$tdt|tsJt|tsJt|tsJtdd}t|trjd}|}||}n |}||}||krtdtddi|_t|}|r||jd<||_||_ ||_ ||_ dS) Nz/Start value MUST be a datetime or date instancez>end_or_duration MUST be a datetime, date or timedelta instancerrz#Start time is greater than end timerrrx) r3rrr,rr rrstartend by_durationduration)rrrend_or_durationrrrr|rrrrs:   zvPeriod.__init__cCs<|j|jkr||S|j|jkr0|jkr8nndSdS)NTF)roverlapsrr4rrrrs   zvPeriod.overlapscCsF|jr&t|jdt|jSt|jdt|jS)N/)rrrr"rrrr#rrrr"s  zvPeriod.to_icalNcCs\z4|d\}}tj||d}tj||d}||fWStk rVtd|YnXdS)NrrzExpected period format, got: )rrzr0rLr,)r/rrrrrrr0s zvPeriod.from_icalcCs,|jr|j|jf}n |j|jf}d|dS)NzvPeriod(r )rrrr)rprrrr$s zvPeriod.__repr__cCs|j|jr|jn|jfS)z-Make this cooperate with the other vDDDTypes.)rrrrr#rrrr}sz vPeriod.dtr)FBTYPE)N)r7r8r9r:r;rrr"r<r0r$rlr}r[rrrrrrfs ?#   rc s\eZdZUdZded<edddddd d d Zeiffd d ZddZ e ddZ Z S)vWeekdaya5Either a ``weekday`` or a ``weekdaynum`` .. code-block:: pycon >>> from icalendar import vWeekday >>> vWeekday("MO") # Simple weekday 'MO' >>> vWeekday("2FR").relative # Second friday 2 >>> vWeekday("2FR").weekday 'FR' >>> vWeekday("-1SU").relative # Last Sunday -1 Definition from `RFC 5545, Section 3.3.10 `_: .. code-block:: text weekdaynum = [[plus / minus] ordwk] weekday plus = "+" minus = "-" ordwk = 1*2DIGIT ;1 to 53 weekday = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA" ;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, ;FRIDAY, and SATURDAY days of the week. r rrrrrr)ZSUZMOZTUZWEZTHZFRZSAc st||d}t||}t|}|dkr:td||}|d}|d}|d}|tjksl|dkrztd||pd|_ |rt |pd|_ |dkr|j r|j d9_ t ||_ |S) NrR#Expected weekday abbrevation, got: signalweekdayrelativez+-rr&)rrCrD WEEKDAY_RULErr, groupdictr week_daysrrrr r) rFrrrrrrrrrIrrrDs"    zvWeekday.__new__cCs|tSrAr)r rr#rrrr"2szvWeekday.to_icalcCs6z||WStk r0td|YnXdS)NrrrLr,rMrrrr05szvWeekday.from_ical) r7r8r9r:r;rrr rDr"rNr0rOrrrIrrs  rc s\eZdZUdZded<edddddd d d Zeiffd d ZddZ e ddZ Z S) vFrequencyz+A simple class that catches illegal values.r rSECONDLYMINUTELYHOURLYDAILYWEEKLYMONTHLYYEARLY)rrrrrrrcs@t||d}t||}|tjkr2td|t||_|S)NrRExpected frequency, got: )rrCrDr frequenciesr,r rrSrIrrrDNs    zvFrequency.__new__cCs|tSrArr#rrrr"VszvFrequency.to_icalcCs6z||WStk r0td|YnXdS)NrrrMrrrr0YszvFrequency.from_ical) r7r8r9r:r;rrr rDr"rNr0rOrrrIrr=s  rcseZdZUdZded<ifddfdd Zdd d d Zed d ddZddZ e fe Z d d ddZ d d ddZ Z S)vMonthafThe number of the month for recurrence. In :rfc:`5545`, this is just an int. In :rfc:`7529`, this can be followed by `L` to indicate a leap month. .. code-block:: pycon >>> from icalendar import vMonth >>> vMonth(1) # first month January vMonth('1') >>> vMonth("5L") # leap month in Hebrew calendar vMonth('5L') >>> vMonth(1).leap False >>> vMonth("5L").leap True Definition from RFC: .. code-block:: text type-bymonth = element bymonth { xsd:positiveInteger | xsd:string } r rzUnion[str, int])rcst|tr||St|trz|r:t|}d}q|ddkrd|ddrdtd|t|dd}d}n d}t|}t ||}||_ t ||_ |S)NFr&LzInvalid month: T) r3rr"decoderTisdigitrr,rCrDleapr r)rFrrZ month_indexrrrIrrrDs    zvMonth.__new__rWrUcCst|dS)zThe ical representation.r%rpr#rrrr"szvMonth.to_icalrTr.cCs||SrArrMrrrr0szvMonth.from_icalcCs(d}dddd}ddddd }tS) NzWhether this is a leap month.boolrUcSs|jSrAZ_leapr#rrrfgetszvMonth.leap..fgetNone)rrVcSs ||_dSrAr)rrrrrfsetszvMonth.leap..fset)locals)docr r rrrrsz vMonth.leapcCs|jjdt|dS) repr(self)rr )rJr7rTr#rrrr$szvMonth.__repr__cCst||jrdndS)z str(self)rr)rrr#rrr__str__szvMonth.__str__)r7r8r9r:r;rDr"rNr0rrlr$rrOrrrIrras  rc@s*eZdZdZdZdZdZejZddZ dS)vSkipaKSkip values for RRULE. These are defined in :rfc:`7529`. OMIT is the default value. Examples: .. code-block:: pycon >>> from icalendar import vSkip >>> vSkip.OMIT vSkip('OMIT') >>> vSkip.FORWARD vSkip('FORWARD') >>> vSkip.BACKWARD vSkip('BACKWARD') OMITFORWARDBACKWARDcCs|jjd|jdS)Nrr )rJr7_name_r#rrrr$szvSkip.__repr__N) r7r8r9r:rrrr __reduce_ex__r$rrrrrs rcseZdZUdZded<dddddd d gZd Zeeeeeeeeee e ee e e e e d Zid fdd ZddZeddZeddddZZS)vRecuraRecurrence definition. Property Name: RRULE Purpose: This property defines a rule or repeating pattern for recurring events, to-dos, journal entries, or time zone definitions. Value Type: RECUR Property Parameters: IANA and non-standard property parameters can be specified on this property. Conformance: This property can be specified in recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component, but it SHOULD NOT be specified more than once. The recurrence set generated with multiple "RRULE" properties is undefined. Description: The recurrence rule, if specified, is used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", and "EXDATE" properties contained within the recurring component. The "DTSTART" property defines the first instance in the recurrence set. The "DTSTART" property value SHOULD be synchronized with the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value not synchronized with the recurrence rule is undefined. The final recurrence set is generated by gathering all of the start DATE-TIME values generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start DATE-TIME values specified by "EXDATE" properties. This implies that start DATE- TIME values specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored. The "DTSTART" property specified within the iCalendar object defines the first instance of the recurrence. In most cases, a "DTSTART" property of DATE-TIME value type used with a recurrence rule, should be specified as a date with local time and time zone reference to make sure all the recurrence instances start at the same local time regardless of time zone changes. If the duration of the recurring component is specified with the "DTEND" or "DUE" property, then the same exact duration will apply to all the members of the generated recurrence set. Else, if the duration of the recurring component is specified with the "DURATION" property, then the same nominal duration will apply to all the members of the generated recurrence set and the exact duration of each recurrence instance will depend on its specific start time. For example, recurrence instances of a nominal duration of one day will have an exact duration of more or less than 24 hours on a day where a time zone shift occurs. The duration of a specific recurrence may be modified in an exception component or simply by using an "RDATE" property of PERIOD value type. Examples: The following RRULE specifies daily events for 10 occurrences. .. code-block:: text RRULE:FREQ=DAILY;COUNT=10 Below, we parse the RRULE ical string. .. code-block:: pycon >>> from icalendar.prop import vRecur >>> rrule = vRecur.from_ical('FREQ=DAILY;COUNT=10') >>> rrule vRecur({'FREQ': ['DAILY'], 'COUNT': [10]}) You can choose to add an rrule to an :class:`icalendar.cal.Event` or :class:`icalendar.cal.Todo`. .. code-block:: pycon >>> from icalendar import Event >>> event = Event() >>> event.add('RRULE', 'FREQ=DAILY;COUNT=10') >>> event.rrules [vRecur({'FREQ': ['DAILY'], 'COUNT': [10]})] r rrrrrrrr)ZRSCALEFREQUNTILCOUNTINTERVALBYSECONDBYMINUTEBYHOURBYDAY BYWEEKDAY BYMONTHDAY BYYEARDAYBYWEEKNOBYMONTHBYSETPOSWKSTSKIP)rrrrrr"r r!r#rr$r%rrrr&r@csp|r.t|dtr.||df|dd}|D]\}}t|ts6|g||<q6tj||t||_dS)Nrr) r3rTr0itemsrrCrr r)rrrGrHkvrIrrrZs  zvRecur.__init__csrg}|D]Z\}}|j|tt|ts2|g}dfdd|D}|t}| |d|q d|S)Nrc3s|]}|VqdSrAr!)r~valtyprrrjsz!vRecur.to_ical..=;) Z sorted_itemstypesrrPr3rrr)r r{)rresultrvalsrr+rr"ds  zvRecur.to_icalcs&|j|tfdd|dDS)Ncsg|]}|qSr)r0)r~r)parserrrrvsz%vRecur.parse_type..r)r/rrPr)rFrvaluesrr2r parse_typerszvRecur.parse_typerTr.c Cst||r|Sz\|}|dD]@}z|d\}}Wntk rNYq YnX|||||<q ||WStk rYntd|YnXdS)N;=zError in recurrence rule: )r3rr,r5)rFr/recurpairsrr1rrrr0xs   zvRecur.from_ical)r7r8r9r:r;rZcanonical_orderrrsrrzrrrr/rr"rNr5r0rOrrrIrrsH S   rc@s,eZdZdZddZddZeddZdS) raTime Value Name: TIME Purpose: This value type is used to identify values that contain a time of day. Format Definition: This value type is defined by the following notation: .. code-block:: text time = time-hour time-minute time-second [time-utc] time-hour = 2DIGIT ;00-23 time-minute = 2DIGIT ;00-59 time-second = 2DIGIT ;00-60 ;The "60" value is used to account for positive "leap" seconds. time-utc = "Z" Description: If the property permits, multiple "time" values are specified by a COMMA-separated list of values. No additional content value encoding (i.e., BACKSLASH character encoding, see vText) is defined for this value type. The "TIME" value type is used to identify values that contain a time of day. The format is based on the [ISO.8601.2004] complete representation, basic format for a time of day. The text format consists of a two-digit, 24-hour of the day (i.e., values 00-23), two-digit minute in the hour (i.e., values 00-59), and two-digit seconds in the minute (i.e., values 00-60). The seconds value of 60 MUST only be used to account for positive "leap" seconds. Fractions of a second are not supported by this format. In parallel to the "DATE-TIME" definition above, the "TIME" value type expresses time values in three forms: The form of time with UTC offset MUST NOT be used. For example, the following is not valid for a time value: .. code-block:: text 230000-0800 ;Invalid time format **FORM #1 LOCAL TIME** The local time form is simply a time value that does not contain the UTC designator nor does it reference a time zone. For example, 11:00 PM: .. code-block:: text 230000 Time values of this type are said to be "floating" and are not bound to any time zone in particular. They are used to represent the same hour, minute, and second value regardless of which time zone is currently being observed. For example, an event can be defined that indicates that an individual will be busy from 11:00 AM to 1:00 PM every day, no matter which time zone the person is in. In these cases, a local time can be specified. The recipient of an iCalendar object with a property value consisting of a local time, without any relative time zone information, SHOULD interpret the value as being fixed to whatever time zone the "ATTENDEE" is in at any given moment. This means that two "Attendees", may participate in the same event at different UTC times; floating time SHOULD only be used where that is reasonable behavior. In most cases, a fixed time is desired. To properly communicate a fixed time in a property value, either UTC time or local time with time zone reference MUST be specified. The use of local time in a TIME value without the "TZID" property parameter is to be interpreted as floating time, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object. **FORM #2: UTC TIME** UTC time, or absolute time, is identified by a LATIN CAPITAL LETTER Z suffix character, the UTC designator, appended to the time value. For example, the following represents 07:00 AM UTC: .. code-block:: text 070000Z The "TZID" property parameter MUST NOT be applied to TIME properties whose time values are specified in UTC. **FORM #3: LOCAL TIME AND TIME ZONE REFERENCE** The local time with reference to time zone information form is identified by the use the "TZID" property parameter to reference the appropriate time zone definition. Example: The following represents 8:30 AM in New York in winter, five hours behind UTC, in each of the three formats: .. code-block:: text 083000 133000Z TZID=America/New_York:083000 cGsXt|dkr>> from icalendar.prop import vUri >>> uri = vUri.from_ical('http://example.com/my-report.txt') >>> uri 'http://example.com/my-report.txt' r rcs(t||d}t||}t||_|SrQr]rSrIrrrDAs  z vUri.__new__cCs |tSrAr^r#rrrr"Gsz vUri.to_icalcCs2z ||WStk r,td|YnXdS)NzExpected , got: rqrMrrrr0Js zvUri.from_ical r7r8r9r:r;r rDr"rNr0rOrrrIrr;s +r;c@sPeZdZUdZded<ifddddZdd Zed d Zd d Z ddZ dS)vGeoaGeographic Position Property Name: GEO Purpose: This property specifies information related to the global position for the activity specified by a calendar component. Value Type: FLOAT. The value MUST be two SEMICOLON-separated FLOAT values. Property Parameters: IANA and non-standard property parameters can be specified on this property. Conformance: This property can be specified in "VEVENT" or "VTODO" calendar components. Description: This property value specifies latitude and longitude, in that order (i.e., "LAT LON" ordering). The longitude represents the location east or west of the prime meridian as a positive or negative real number, respectively. The longitude and latitude values MAY be specified up to six decimal places, which will allow for accuracy to within one meter of geographical position. Receiving applications MUST accept values of this precision and MAY truncate values of greater precision. Example: .. code-block:: text GEO:37.386013;-122.082932 Parse vGeo: .. code-block:: pycon >>> from icalendar.prop import vGeo >>> geo = vGeo.from_ical('37.386013;-122.082932') >>> geo (37.386013, -122.082932) Add a geo location to an event: .. code-block:: pycon >>> from icalendar import Event >>> event = Event() >>> latitude = 37.386013 >>> longitude = -122.082932 >>> event.add('GEO', (latitude, longitude)) >>> event['GEO'] vGeo((37.386013, -122.082932)) r rz+tuple[float | str | int, float | str | int])geoc Csnz&|d|d}}t|}t|}Wn,tk rR}ztd|W5d}~XYnX||_||_t||_dS)zCreate a new vGeo from a tuple of (latitude, longitude). Raises: ValueError: if geo is not a tuple of (latitude, longitude) rrz7Input must be (float, float) for latitude and longitudeN)floatrLr,latitude longituder r)rr>rr@rArrrrrs z vGeo.__init__cCs|jd|jS)Nr6)r@rAr#rrrr"sz vGeo.to_icalc CsXz |d\}}t|t|fWStk rR}ztd||W5d}~XYnXdS)Nr6zExpected 'float;float' , got: )rr?rLr,)r/r@rArrrrr0s zvGeo.from_icalcCs||kSrAr!r4rrrr6sz vGeo.__eq__cCs|jjd|jd|jdS)rz((rz)))rJr7r@rAr#rrrr$sz vGeo.__repr__Nrrrrrr=Rs : r=c@sVeZdZUdZded<dZifddZddZed d Z d d Z d dZ ddZ dS) vUTCOffsetaiUTC Offset Value Name: UTC-OFFSET Purpose: This value type is used to identify properties that contain an offset from UTC to local time. Format Definition: This value type is defined by the following notation: .. code-block:: text utc-offset = time-numzone time-numzone = ("+" / "-") time-hour time-minute [time-second] Description: The PLUS SIGN character MUST be specified for positive UTC offsets (i.e., ahead of UTC). The HYPHEN-MINUS character MUST be specified for negative UTC offsets (i.e., behind of UTC). The value of "-0000" and "-000000" are not allowed. The time-second, if present, MUST NOT be 60; if absent, it defaults to zero. Example: The following UTC offsets are given for standard time for New York (five hours behind UTC) and Geneva (one hour ahead of UTC): .. code-block:: text -0500 +0100 .. code-block:: pycon >>> from icalendar.prop import vUTCOffset >>> utc_offset = vUTCOffset.from_ical('-0500') >>> utc_offset datetime.timedelta(days=-1, seconds=68400) >>> utc_offset = vUTCOffset.from_ical('+0100') >>> utc_offset datetime.timedelta(seconds=3600) r rFcCs&t|tstd||_t||_dS)Nz)Offset value MUST be a timedelta instancerrrrrrs zvUTCOffset.__init__cCs|jtdkr"d}td|j}n d}|j}|j|j}}t|d|d}t|dd}t|d}|r|d|d|d}n|d|d}||S)Nrz-%sz+%srrr)rrrrr)rrrrrrrrrrrr"s zvUTCOffset.to_icalcCst||r|jSzV|ddt|ddt|ddt|ddpHdf\}}}}t|||d}Wn"tk rtd|YnX|js|tdd krtd ||d kr| S|S) Nrrrrr_)rrrzExpected utc offset, got: rC)rz'Offset must be less than 24 hours, was r)r3rrrrLr,ignore_exceptions)rFr/rrrroffsetrrrr0s    zvUTCOffset.from_icalcCst|tsdS|j|jkSr)r3rBrr4rrrr6s zvUTCOffset.__eq__cCs t|jSrA)rrr#rrrrszvUTCOffset.__hash__cCsd|jdS)Nz vUTCOffset(r rr#rrrr$"szvUTCOffset.__repr__N) r7r8r9r:r;rDrr"rNr0r6rr$rrrrrBs /  rBcsDeZdZUdZded<eiffdd ZddZedd Z Z S) vInlinezThis is an especially dumb class that just holds raw unparsed text and has parameters. Conversion of inline values are handled by the Component class, so no further processing is needed. r rcs(t||d}t||}t||_|SrQr]rSrIrrrD.s  zvInline.__new__cCs |tSrAr^r#rrrr"4szvInline.to_icalcCs||SrArrMrrrr07szvInline.from_icalr<rrrIrrF&s rFcEseZdZdZfddZeddddddddddddddddd d d d d d dddd d dd dd d dddddddddd d d d d dddddd d dddddd ddddddd ddCZddZddZddZ Z S) TypesFactoryzAll Value types defined in RFC 5545 are registered in this factory class. The value and parameter names don't overlap. So one factory is enough for both kinds. cstj||tttttttt t t t t tttttttttf|_t|d<t|d<t|d<t|d<t|d<t|d<t |d<t|d<t|d <t|d <t|d <t|d <t|d <t|d<t |d<t |d<t|d<t|d<dS)z"Set keys to upper for initial dictbinaryboolean cal-addressr date-timerr?integerperiodr8textruri utc-offsetr>inlinedate-time-list categoriesN)rCrrr=r\rtrzrrrrnrr=rFrsrrrPrrBr;rrZ all_types)rrGrHrIrrrDsRzTypesFactory.__init__rNrOrSr>rLrKrrMrPrJrRr8rI)CZcalscalemethodZprodidversionattachrSclasscomment descriptionr>locationzpercent-completepriority resourcesstatussummaryZ completedZdtendZdueZdtstartrZfreebusyZtranspr|tznameZ tzoffsetfromZ tzoffsettoZtzurlZattendeecontactZ organizerz recurrence-idz related-tourluidZexdateZexruleZrdateZrruleactionrepeatZtriggerZ acknowledgedcreatedZdtstampz last-modifiedsequencezrequest-statusZaltrepZcnZcutypezdelegated-fromz delegated-todirrZfmttypeZfbtypelanguagememberZpartstatrangerelatedZreltyperoleZrsvpzsent-byrcCs||j|dS)z6Returns a the default type for a property or parameterrN) types_mapr)rrmrrr for_propertyszTypesFactory.for_propertycCs||}||S)zcEncodes a named value from a primitive python type to an icalendar encoded string. )rnr")rrmr type_classrrrr"s zTypesFactory.to_icalcCs||}||}|S)zyDecodes a named property or parameter value from an icalendar encoded string to a primitive python type. )rnr0)rrmrrodecodedrrrr0s  zTypesFactory.from_ical) r7r8r9r:rrrmrnr"r0rOrrrIrrG<s 1UrGrrrr)>r: __future__rr*r'rerrrrtypingrZicalendar.caselessdictrZicalendar.enumsr Zicalendar.parserr r r Zicalendar.parser_toolsr rrrrrrrrcompilerrrrr=rTrPr\r?rnrsrtrrrzrrrrrrrrrrr;r=rBrFrG__all__rrrrs,    ;X@C0"?LPI$P??br$