➜

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 belopolsky
Recipients Alexander.Belopolsky, Anders.Hovmöller, Arfrever, belopolsky, cvrebert, eric.araujo, flying sheep, jcea, kirpit, mcepl, nagle, r.david.murray, roysmith
Date 2013-03-11.05:06:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362978412.68.0.907216938627.issue15873@psf.upfronthosting.co.za>
In-reply-to
Content 
Éric> do you think there is a need to check python-ideas or python-dev before working on this?

Yes, I think this is python-ideas material.  IMHO, what should be added to datetime module in 3.4 is ability to construct date/time objects from their str() representation:

assert time(str(t)) == t
assert date(str(d)) == d
assert datetime(str(dt)) == dt

I am not sure the same is needed for timedelta, but this can be discussed.

Implementation of any external to python standard should be wetted at PyPI first.  There may be a reason why there is no rfc3339.py module on PyPI.
History
Date User Action Args
2013-03-11 05:06:52belopolskysetrecipients: + belopolsky, jcea, roysmith, nagle, mcepl, eric.araujo, Arfrever, r.david.murray, cvrebert, Alexander.Belopolsky, flying sheep, kirpit, Anders.Hovmöller
2013-03-11 05:06:52belopolskysetmessageid: <1362978412.68.0.907216938627.issue15873@psf.upfronthosting.co.za>
2013-03-11 05:06:52belopolskylinkissue15873 messages
2013-03-11 05:06:52belopolskycreate