+ j#Rt^RIt^RIHtHtHtHt^RIHtHt^RI H t ^RI H t ^RI Ht^RIHt^RIHt^R IHt]P*!R 4t!R R ]4tR .tR#) z$TIME property type from :rfc:`5545`.N)datetimetimetimezonetzinfo)AnyClassVar)Self)JCalParsingError) Parameters)tzp)is_utc)TimeBasezJ^(?P[0-9]{2}):(?P[0-9]{2}):(?P[0-9]{2})(?PZ)?\Zca]tRt^toRtRtRR/V3RlRlltRtV3RlR lt] RV3R lR ll4t ] V3R lR l4t ^RI HtV3RlRlt] V3RlRl4t] V3RlRl4tV3RltRtVtR#)vTimeaTime 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:: ics 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:: ics 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:: ics 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:: ics 083000 133000Z TZID=America/New_York:083000 TIMEparamsNcN<V^8dQhRS[RS[S[S[3,R,RR/#)argsrNreturn)rdictstr)format __classdict__s"U/home/ralf/ical-fahrzeuge/venv/lib/python3.14/site-packages/icalendar/prop/dt/time.py __annotate__vTime.__annotate__s/..c.4S>D+@.D.cN\V4^8XdH\V^,\\34'g\ RV^, 24hV^,VnM\V!Vn\ T;'g/4VnVPPVP 4R#)zExpected a datetime.time, got: N) len isinstancerr ValueErrordtr rupdate_tzid_from)selfrrs&$*r__init__vTime.__init__sx t9>d1gh'788 #B47)!LMM1gDGDkDG 2.  $$TWW-rczVPPR4pVP4'd VR, pV#)z%H%M%SZ)r#strftimer )r%values& rto_ical vTime.to_icals/  * ;;== SLE rc <V^8dQhRS[/#rr)bool)rrs"rrrs777rc pVPP4;'g\VP4#)zWhether this time is UTC.)rr r#)r%s&rr vTime.is_utcs%{{!!#66vdgg6rcJ<V^8dQhRS[RS[R,S[,RS[/#)ricalrNr)rrr)rrs"rrrs0(C(C(CsTzF':(Cd(Crc Rp\V\4'd\P!V4pMVeTp\V\4'dVP 4pVP R4^,pVPR4;p'dVRRp\V4^8wg-VP4'dVP4'g\RV 24h\VR,4\VR,4\VR,43pV'd\P!\V!V4#V'd\P!\V!4#\V!# \ dp\RT 24ThRp?ii;i) aConvert an ical string into a time. This method supports parsing the three forms of time values defined in :rfc:`5545#section-3.3.12`: - Local time (floating) - UTC time - Local time with time zone reference Returns: A :class:`datetime.time` object representing the parsed time, with timezone information if applicable. Raises: ValueError: if the provided string cannot be parsed as a time. N:r)zExpected time, got: :NrN:rN:r7N)r!rr rbytesdecode rpartitionendswithr isasciiisdigitr"intlocalizer localize_utc Exception)r4rrutc timetuplees&& r from_icalvTime.from_icals= h $ $\\(+F  !F dE " ";;=Ds#A&--$ $3 $9D t9>t||~~3D6:; ; CT"XDIDIGI||D)$4f==''i(899# # C3D6:; B Cs+AE&8E&E&E&& F1FFc0<V^8dQhRS[S[,/#r/listr)rrs"rrrs##d#rc (V!\^ ^44.#)zExamples of vTime.)r)clss&rexamplesvTime.examplessDRL!""r)VALUEc&<V^8dQhRS[RS[/#)rnamer)rrK)rrs"rrrsXXCXDXrc VPPR4pVP4'd VR, pWPP RR7VP P 4V.#)zBThe jCal representation of this property according to :rfc:`7265`.z%H:%M:%Sr)T) exclude_utc)r#r*r rto_jcalrPlower)r%rRr+s&& rrU vTime.to_jcalsW  , ;;== SLEkk))d);TZZ=M=M=OQVWWrc&<V^8dQhRS[RS[/#)rjcalr)rr)rrs"rrrsPPCPDPrc \P!V\V4\P V4pVf\RWR7h\ VP R44p\ VP R44p\ VP R44p\VP R44p\Y4YV'd\PR7#RR7#) zqParse a jCal string to a :class:`datetime.time`. Raises: ~error.JCalParsingError: If it can't parse a time. NzCannot parse time.)r+hourminutesecondrD)r) r validate_value_typerTIME_JCAL_REGEXmatchr@groupr0rrrD)rMrYr`r[r\r]rDs&& rparse_jcal_valuevTime.parse_jcal_values ,,T3<%%d+ ="#7I I5;;v&'U[[*+U[[*+5;;u%&D&OO$OOrc&<V^8dQhRS[RS[/#)r jcal_propertyrrJ)rrs"rrrs  d t rc \P!W4\P!^4;_uu_4VPV^,4pRRR4V!X\P !V4R7# +'giL.;i)zParse jCal from :rfc:`7265`. Parameters: jcal_property: The jCal property to parse. Raises: ~error.JCalParsingError: If the provided jCal is invalid. N)r)r validate_propertyreraise_with_path_addedrbr from_jcal_property)rMrer+s&& r from_jcalvTime.from_jcalsd **=>  5 5a 8 8((q)9:E9 00?  9 8s A44 B cB<V^8dQh/S[S[,;R&S[;R&#)r default_valuer)rrr )rrs"rrrs'`C=)ab cr)r#r)N)__name__ __module__ __qualname____firstlineno____doc__rmr&r,r staticmethodrG classmethodrNicalendar.paramrPrUrbrj__annotate_func____static_attributes____classdictcell__)rs@rrrsm^$*M.4.. 77(C(C(CT##&XXPP   err)rrrerrrrtypingrricalendar.compatibilityricalendar.errorr icalendar.parserr icalendar.timezoner icalendar.timezone.tzidr baser compiler_r__all__rrrsO* 55 (,'"***Q a Ha H )r