Re: About w3cdate datetime format

Wari Wahab <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user
Message-ID <[email protected]>
limodou wrote:

>Wari Wahab,您好!
>
>	I check the url and found that:
>
><dateTime.iso8601> date/time 19980717T14:08:55 
>
>it's not same as used in base.py in pyblosxom. I mean the usage of datetime in pyblosxom may be not standard. What do you think?
>  
>
w3cdate <= (is a subset of) iso8601.

Anyway, xmlrpc protocol will die if we put the Z at the end. At the time
of writing, I tested the w3cdate variable with a lot of software on the
net, and the form: %Y-%m-%dT%H:%M:%SZ is the most compatible with all of
the software out there. Another reason for the 'Z' is the fact that I
cannot get the proper time offset from the stock python libraries (which
is based on the unix time library). I can always substitute 'Z' with
+00:00, but that wouldn't be ethical :) You can learn more about the
w3cdate a.k.a. iso8601 on http://www.cs.tut.fi/~jkorpela/iso8601.html
which outlines all the possibilities of the format.


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.