Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Pete Forman Newsgroups: comp.lang.python Subject: Re: Parsing ISO date/time strings - where did the parser go? Date: Wed, 12 Sep 2012 13:31:14 +0100 Organization: A noiseless patient Spider Lines: 27 Message-ID: <86txv3fmnh.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: mx04.eternal-september.org; posting-host="51eb60163f8767c8f0599490068f460a"; logging-data="13428"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX187uDPT/NcvuBt6Y7gphGmF" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (windows-nt) X-Antivirus-Status: Clean X-Antivirus: avast! (VPS 120912-0, 09/12/2012), Outbound message Cancel-Lock: sha1:taRU2cpXBRixqBadq4hHtRppKNo= sha1:hmUKoiOHaWn0/hfy5mXKiEHMPBY= Xref: csiph.com comp.lang.python:28951 John Nagle writes: > I want to parse standard ISO date/time strings such as > > 2012-09-09T18:00:00-07:00 > > into Python "datetime" objects. Consider whether RFC 3339 might be a more suitable format. It is a subset of ISO 8601 extended format. Some of the restrictions are Year must be 4 digits Fraction separator is period, not comma All components including time-offset are mandatory, except for time-secfrac time-minute in time-offset is not optional, must use ±hh:mm or Z Some latitude is allowed T may be replaced by e.g. space Extra feature time-offset of -00:00 means UTC but local time is unknown -- Pete Forman