Re: Parsing ISO date/time strings - where did the parser go?

Path	csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!newsfeed.freenet.ag!news2.euro.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path	<jdgleeson@mac.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.002
X-Spam-Evidence	'H': 1.00; 'S': 0.00; 'x-mailer:apple mail (2.936)': 0.04; 'parser': 0.07; 'pypi': 0.07; 'try:': 0.07; 'encoding.': 0.09; 'cc:addr:python-list': 0.10; '0.1dev': 0.16; '0.2.0': 0.16; 'received:mac.com': 0.16; 'should.': 0.16; 'subject:ISO': 0.16; 'subject:parser': 0.16; 'subject:where': 0.16; 'wrote:': 0.17; 'module': 0.19; 'parse': 0.22; 'received:192.168.1.100': 0.22; 'cc:20': 0.23; 'cc:no real name:20': 0.24; 'cc:addr:python.org': 0.25; 'subject:/': 0.28; 'aims': 0.29; 'dates': 0.33; 'utility': 0.33; 'updated': 0.34; 'received:17': 0.35; 'pm,': 0.35; 'subject:?': 0.35; 'charset:us- ascii': 0.36; 'subject:: ': 0.38; 'some': 0.38; 'received:192': 0.39; 'received:192.168': 0.40; 'john': 0.60; 'more': 0.63; 'here': 0.65; 'offers:': 0.91
MIME-version	1.0
Content-transfer-encoding	7BIT
Content-type	text/plain; CHARSET=US-ASCII; format=flowed; delsp=yes
X-Proofpoint-Virus-Version	vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-09-08_08:2012-09-06, 2012-09-08, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details	rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1209080262
From	John Gleeson <jdgleeson@mac.com>
To	John Nagle <nagle@animats.com>
In-reply-to	<k2b1ca$tc6$1@dont-email.me>
Subject	Re: Parsing ISO date/time strings - where did the parser go?
Date	Sat, 08 Sep 2012 18:20:25 -0600
References	<k2atej$4rq$1@dont-email.me> <7xbohj3p6e.fsf@ruckus.brouhaha.com> <k2b1ca$tc6$1@dont-email.me>
X-Mailer	Apple Mail (2.936)
Cc	python-list@python.org
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.15
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.399.1347153638.27098.python-list@python.org> (permalink)
Lines	21
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1347153638 news.xs4all.nl 6876 [2001:888:2000:d::a6]:52485
X-Complaints-To	abuse@xs4all.nl
Xref	csiph.com comp.lang.python:28751

Show key headers only | View raw

On 2012-09-06, at 2:34 PM, John Nagle wrote:
>  Yes, it should.  There's no shortage of implementations.
> PyPi has four.  Each has some defect.
>
>   PyPi offers:
>
> 	iso8601 0.1.4 		Simple module to parse ISO 8601 dates
> 	iso8601.py 0.1dev 	Parse utilities for iso8601 encoding.
> 	iso8601plus 0.1.6 	Simple module to parse ISO 8601 dates
> 	zc.iso8601 0.2.0 	ISO 8601 utility functions


Here are three more on PyPI you can try:

iso-8601 0.2.3           Flexible ISO 8601 parser...
PySO8601 0.1.7       PySO8601 aims to parse any ISO 8601 date...
isodate 0.4.8            An ISO 8601 date/time/duration parser and  
formater

All three have been updated this year.

Thread

Parsing ISO date/time strings - where did the parser go? John Nagle <nagle@animats.com> - 2012-09-06 12:27 -0700
  Re: Parsing ISO date/time strings - where did the parser go? Paul Rubin <no.email@nospam.invalid> - 2012-09-06 12:51 -0700
    Re: Parsing ISO date/time strings - where did the parser go? John Nagle <nagle@animats.com> - 2012-09-06 13:34 -0700
      Re: Parsing ISO date/time strings - where did the parser go? Miki Tebeka <miki.tebeka@gmail.com> - 2012-09-06 16:27 -0700
      Re: Parsing ISO date/time strings - where did the parser go? John Gleeson <jdgleeson@mac.com> - 2012-09-08 18:20 -0600
        Re: Parsing ISO date/time strings - where did the parser go? John Nagle <nagle@animats.com> - 2012-09-08 20:51 -0700
          Re: Parsing ISO date/time strings - where did the parser go? Roy Smith <roy@panix.com> - 2012-09-09 06:15 -0400
            Re: Parsing ISO date/time strings - where did the parser go? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-09-09 12:20 +0100
  Re: Parsing ISO date/time strings - where did the parser go? Thomas Jollans <t@jollybox.de> - 2012-09-06 21:44 +0200
    Re: Parsing ISO date/time strings - where did the parser go? Roy Smith <roy@panix.com> - 2012-09-09 08:14 -0400
      Re: Parsing ISO date/time strings - where did the parser go? "Rhodri James" <rhodri@wildebst.demon.co.uk> - 2012-09-10 22:46 +0100
        Re: Parsing ISO date/time strings - where did the parser go? Chris Angelico <rosuav@gmail.com> - 2012-09-11 08:51 +1000
          Re: Parsing ISO date/time strings - where did the parser go? Roy Smith <roy@panix.com> - 2012-09-10 21:12 -0400
            Re: Parsing ISO date/time strings - where did the parser go? Ben Finney <ben+python@benfinney.id.au> - 2012-09-12 02:00 +1000
  Re: Parsing ISO date/time strings - where did the parser go? Dave Angel <d@davea.name> - 2012-09-06 15:54 -0400
    Re: Parsing ISO date/time strings - where did the parser go? Roy Smith <roy@panix.com> - 2012-09-06 19:44 -0400
      Re: Parsing ISO date/time strings - where did the parser go? André Malo <ndparker@gmail.com> - 2012-09-08 20:12 +0200
  Re: Parsing ISO date/time strings - where did the parser go? Roy Smith <roy@panix.com> - 2012-09-06 19:34 -0400
  Re: Parsing ISO date/time strings - where did the parser go? Terry Reedy <tjreedy@udel.edu> - 2012-09-06 22:12 -0400
  Re: Parsing ISO date/time strings - where did the parser go? Pete Forman <petef4+usenet@gmail.com> - 2012-09-12 13:31 +0100

csiph-web