[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-29 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- status: open -> closed versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-li

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-16 Thread Iakov Davydov
Iakov Davydov added the comment: I took a closer look for #15873. Apperently it solves the issue. Thanks, David. -- ___ Python tracker ___

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-16 Thread R. David Murray
R. David Murray added the comment: Supporting ISO 8601 is quite different from supporting RFC2822 dates, as far as I can see, and the latter clearly belongs in the email library (especially considering that RFC2822 parsing must follow Postel's Law and accept "dirty" data). If you want to op

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-16 Thread Iakov Davydov
Iakov Davydov added the comment: ISO 8601 is meant as the standard way to provide an unambiguous and well-defined method of representing dates and times. And the fact that it is widely used in e-mails doesn't make it e-mail specific. Incorporating function parsedate_to_datetime to email.util i

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-16 Thread R. David Murray
Changes by R. David Murray : -- resolution: -> duplicate stage: test needed -> resolved ___ Python tracker ___ ___ Python-bugs-list ma

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-16 Thread R. David Murray
R. David Murray added the comment: Yes, I think that is appropriate. Note that you also get RFC822 parsing for datetime via email.util.parsedate_to_datetime. (I'm not sure why the OP thought that using the email utilities to parse email-standard dates was "not [a] very good way".) --

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-15 Thread Martin Panter
Martin Panter added the comment: For RFC 2822, perhaps email.utils.parsedate() is good enough? For RFC 3339, Issue 15873 has been opened for the "datetime" module. It has more discussion and code, so perhaps this bug can be closed as a duplicate? -- ___

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-06-15 Thread Martin Panter
Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-03-13 Thread Tin Tvrtković
Changes by Tin Tvrtković : -- nosy: +tinchester ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-03-11 Thread Chris Rebert
Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2013-04-02 Thread Berker Peksag
Changes by Berker Peksag : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2013-04-01 Thread Mark Lawrence
Mark Lawrence added the comment: I've no idea if this is of any use but thought I'd reference it anyway https://pypi.python.org/pypi/strict-rfc3339 -- nosy: +BreamoreBoy ___ Python tracker _

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2010-11-18 Thread Mihai Capotă
Changes by Mihai Capotă : -- nosy: +mihaic ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2010-06-11 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: %O is used by POSIX spec to indicate alternative locale format. Gnu date uses %:z %:z+hh:mm numeric timezone (e.g., -04:00) %::z +hh:mm:ss numeric time zone (e.g., -04:00:00) %:::z numeric time zone with : to ne

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2010-04-08 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2010-04-08 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2010-01-15 Thread R. David Murray
R. David Murray added the comment: I mean issue 665194. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2010-01-15 Thread R. David Murray
R. David Murray added the comment: See also issue 655194. -- nosy: +r.david.murray priority: -> normal stage: -> test needed versions: +Python 3.2 ___ Python tracker ___ __

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2009-09-17 Thread Matías Ribecky
Changes by Matías Ribecky : -- nosy: +mribecky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5207] extend strftime/strptime format for RFC3339 and RFC2822

2009-02-10 Thread Iakov Davydov
New submission from Iakov Davydov : 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 speci