a oe @s6ddlZddlmZddlZddlmZdddZdS)N)datetime) FixedOffsetFc CstdtjtjB}||}|dur|ddvrL|durDd}q|tj}n0|dur^tdnt t |dt |d}|d }|durd }nt t t |d }t t |d t |d t |dt |dt |dt |d||d}|r|tj}|StddS)a Parse an :RFC:`3339`-formatted timestamp and return a `datetime.datetime`. If the timestamp is presented in UTC, then the `tzinfo` parameter of the returned `datetime` will be set to `pytz.utc`. >>> parse('2009-01-01T10:01:02Z') datetime.datetime(2009, 1, 1, 10, 1, 2, tzinfo=) Otherwise, a `tzinfo` instance is created with the appropriate offset, and the `tzinfo` parameter of the returned `datetime` is set to that value. >>> parse('2009-01-01T14:01:02-04:00') datetime.datetime(2009, 1, 1, 14, 1, 2, tzinfo=) However, if `parse()` is called with `utc=True`, then the returned `datetime` will be normalized to UTC (and its tzinfo parameter set to `pytz.utc`), regardless of the input timezone. >>> parse('2009-01-01T06:01:02-04:00', utc=True) datetime.datetime(2009, 1, 1, 10, 1, 2, tzinfo=) The input is strictly required to conform to :RFC:`3339`, and appropriate exceptions are thrown for invalid input. >>> parse('2009-01-01T06:01:02') Traceback (most recent call last): ... ValueError: timestamp does not conform to RFC 3339 >>> parse('2009-01-01T25:01:02Z') Traceback (most recent call last): ... ValueError: hour must be in 0..23 aB^(?:(?:(?P[0-9]{4})\-(?P[0-9]{2})\-(?P[0-9]{2}))T(?:(?:(?P[0-9]{2})\:(?P[0-9]{2})\:(?P[0-9]{2})(?P(?:\.[0-9]{1,}))?)(?P(?:Z|(?P(?P(?:\+|\-)[0-9]{2})\:(?P[0-9]{2}))))))$NZ time_offset)Zzz+00:00z-00:00Tz6cannot produce a naive datetime from a local timestampZtime_houroffsetZtime_minuteoffsetZ time_secfracri@BZ date_fullyearZ date_monthZ date_mdayZ time_hourZ time_minuteZ time_second)ZyearZmonthZdayZhourZminutesecond microsecondtzinfoz×tamp does not conform to RFC 3339)recompileIXmatchgrouppytzutc ValueErrorrintroundfloatrZ astimezone) Z timestamprZ produce_naiveZparse_rer rZsecfracrZdt_outr1C:\Program Files\Certbot\pkgs\pyrfc3339\parser.pyparse s>'             r)FF)r rrZpyrfc3339.utilsrrrrrrs