This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author daniel.urban
Recipients ajaksu2, daniel.urban, eric.araujo, l0nwlf, techtonik
Date 2010-04-29.19:55:53
SpamBayes Score 0.0026926196
Marked as misclassified No
Message-id <>
> I do not think that -00:00 or +00:00 will be invalid Atom timestamp,
> but to implement parser of rfc3339 timestamp, Z handling is still
> needed. I can easily imagine people making wrong assumption that
> parsing 00:00 at the end would be enough for proper round-tripping.

I can't follow you. This issue and my patch is about creating a string in RFC 3339 format, not *parsing*.
Date User Action Args
2010-04-29 19:55:55daniel.urbansetrecipients: + daniel.urban, techtonik, ajaksu2, eric.araujo, l0nwlf
2010-04-29 19:55:55daniel.urbansetmessageid: <>
2010-04-29 19:55:53daniel.urbanlinkissue7584 messages
2010-04-29 19:55:53daniel.urbancreate