Message 81565 - Python tracker

➜

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	davydov
Recipients	davydov
Date	2009-02-10.17:06:01
SpamBayes Score	0.003635833
Marked as misclassified	No
Message-id	<1234285622.79.0.0309055191852.issue5207@psf.upfronthosting.co.za>
In-reply-to

Content
Currently there is no obvious way to parse time from ISO 8601/W3C/RFC3339 date&time format (http://www.ietf.org/rfc/rfc3339.txt) or RFC2822. (Actually RFC2822 could be parsed with rfc822 module but that is not very good way). I suggest that we should add special directive (let's say %o) for time offset which is "Z" or ("+" / "-") time-hour ":" time-minute. Also %O directive will parse zone: ( "+" / "-" ) time-hour time-minute. (I suppose there is no need to support obsolate time zones but if that is possible it's also good idea).

Currently there is no obvious way to parse time from ISO
8601/W3C/RFC3339 date&time format (http://www.ietf.org/rfc/rfc3339.txt)
or RFC2822. (Actually RFC2822 could be parsed with rfc822 module but
that is not very good way).

I suggest that we should add special directive (let's say %o) for time
offset which is "Z" or ("+" / "-") time-hour ":" time-minute.

Also %O directive will parse zone:  ( "+" / "-" ) time-hour time-minute.
(I suppose there is no need to support obsolate time zones but if that
is possible it's also good idea).

History
Date	User	Action	Args
2009-02-10 17:07:02	davydov	set	recipients: + davydov
2009-02-10 17:07:02	davydov	set	messageid: <1234285622.79.0.0309055191852.issue5207@psf.upfronthosting.co.za>
2009-02-10 17:06:02	davydov	link	issue5207 messages
2009-02-10 17:06:01	davydov	create