Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
status: open - closed
versions: +Python 3.5 -Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
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.)
--
Changes by R. David Murray rdmur...@bitdance.com:
--
resolution: - duplicate
stage: test needed - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
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
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
Iakov Davydov added the comment:
I took a closer look for #15873. Apperently it solves the issue.
Thanks, David.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list
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?
--
Changes by Tin Tvrtković tinches...@gmail.com:
--
nosy: +tinchester
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: -BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Changes by Berker Peksag berker.pek...@gmail.com:
--
versions: +Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
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 rep...@bugs.python.org
http://bugs.python.org/issue5207
Changes by Mihai Capotă mi...@mihaic.ro:
--
nosy: +mihaic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list mailing list
Alexander Belopolsky belopol...@users.sourceforge.net 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
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list mailing
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list
R. David Murray rdmur...@bitdance.com added the comment:
See also issue 655194.
--
nosy: +r.david.murray
priority: - normal
stage: - test needed
versions: +Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
R. David Murray rdmur...@bitdance.com added the comment:
I mean issue 665194.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Changes by Matías Ribecky m...@mribecky.com.ar:
--
nosy: +mribecky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5207
___
___
Python-bugs-list
New submission from Iakov Davydov da...@myths.ru:
Currently there is no obvious way to parse time from ISO
8601/W3C/RFC3339 datetime 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
21 matches
Mail list logo