Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.019 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'pages.': 0.07; 'defined,': 0.09; 'rfc': 0.09; 'sep': 0.09; ':-)': 0.13; '2822': 0.16; 'forty': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'roy': 0.16; 'subject:ISO': 0.16; 'subject:parser': 0.16; 'subject:where': 0.16; 'wrote:': 0.17; '>>>': 0.18; 'received:209.85.214.174': 0.21; 'header:In-Reply- To:1': 0.25; 'am,': 0.27; 'message-id:@mail.gmail.com': 0.27; 'subject:/': 0.28; '+0100,': 0.29; 'long.': 0.29; 'could': 0.32; '11,': 0.33; 'to:addr:python-list': 0.33; 'received:google.com': 0.34; 'subject:?': 0.35; 'received:209.85': 0.35; 'but': 0.36; 'two': 0.37; 'received:209': 0.37; 'subject:: ': 0.38; 'to:addr:python.org': 0.39; 'received:209.85.214': 0.39; 'takes': 0.39; 'short': 0.39; 'header:Received:5': 0.40; 'dead': 0.62; 'thomas': 0.62; 'more': 0.63; 'fact,': 0.69; 'internet': 0.71; 'smith': 0.71; 'article': 0.78; 'stamp': 0.91 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=RZcxdd1tcnFLtdvNk0NiQxum/gyk3N7CFnwDJ7L4aKM=; b=e+nzf8/Jz8zzzfQa9DNItf0OtHCmkk/ocafZ3JQSVylyAn33r9Nb2Big2l3nmF/PSB 10mf2ZbKqJRrZFmbhhEY0AnBau1mtGfy4wrfUNgqO93iB3+uz4XwN3k5L3Ahh8Q7Omd5 /6yvcUjuuXX9w6LRPNJQ8gYbyv6FneZwBFagiiCD5gvbnOFD/bPTfe9mkzCaQRAbP1ob x+BtPk1ryfVWESxjzgQzcEs8xQFgtO+cEt+Blq2OkzykHtww7gOkLyk53oOBczkDDPcq T7AUboAn5RoG4MZzpw4J59ubotztuSb4z+o43/RjccVGIO+DZIRcjHWd1i3djZSKCgOC BlnA== MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 11 Sep 2012 08:51:02 +1000 Subject: Re: Parsing ISO date/time strings - where did the parser go? From: Chris Angelico To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 24 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1347317852 news.xs4all.nl 6856 [2001:888:2000:d::a6]:40104 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:28864 On Tue, Sep 11, 2012 at 7:46 AM, Rhodri James wrote: > On Sun, 09 Sep 2012 13:14:30 +0100, Roy Smith wrote: > >> In article , >> Thomas Jollans wrote: >> >>> The ISO date/time format is dead simple and well-defined. > > >> Well defined, perhaps. But nobody who has read the standard could call >> it "dead simple". ISO-8601-2004(E) is 40 pages long. > > > A short standard, then :-) What is it that takes up forty pages? RFC 2822 describes a date/time stamp in about two pages. In fact, the whole RFC describes the Internet Message Format in not much more than 40 pages. Is ISO-language just bloated? *boggle* ChrisA