Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.octanews.net!indigo.octanews.net!auth.brown.octanews.com.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.python
Subject: Re: Parsing ISO date/time strings - where did the parser go?
References: <k2atej$4rq$1@dont-email.me>
Date: Thu, 06 Sep 2012 12:51:37 -0700
Message-ID: <7xbohj3p6e.fsf@ruckus.brouhaha.com>
Organization: Nightsong/Fort GNOX
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:tv4hRKXW/SBM8vcCHa1novjROOk=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 11
NNTP-Posting-Date: 06 Sep 2012 14:51:37 CDT
X-Complaints-To: abuse@octanews.net
Xref: csiph.com comp.lang.python:28631

John Nagle <nagle@animats.com> writes:
> There's an iso8601 module on PyPi, but it's abandoned; it hasn't been
> updated since 2007 and has many outstanding issues.

Hmm, I have some code that uses ISO date/time strings and just checked
to see how I did it, and it looks like it uses iso8601-0.1.4-py2.6.egg .
I don't remember downloading that module (I must have done it and
forgotten).  I'm not sure what its outstanding issues are, as it works
ok in the limited way I use it.

I agree that this functionality ought to be in the stdlib.