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 roysmith
Recipients Alexander.Belopolsky, Arfrever, belopolsky, cvrebert, nagle, r.david.murray, roysmith
Date 2012-09-09.12:15:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347192903.1.0.815479107193.issue15873@psf.upfronthosting.co.za>
In-reply-to
Content
We need to define the scope of what input strings will be accepted.  ISO-8601 defines a lot of stuff which we may not wish to accept.

Do we want to accept both basic format (YYYYMMDD) and extended format (YYYY-MM-DD)?

Do we want to accept things like "1985-W15-5", which is (if I understand this correctly(), the 5th day of the 15th week of 1985 [section 4.1.4.2].

Do we want to accept [section 4.2.2.4], "23:20,8", which is 23 hours, 20 minutes, 8 tenths of a minute.

I suspect most people who have been following the recent thread (https://groups.google.com/d/topic/comp.lang.python/Q2w4R89Nq1w/discussion) would say none of the above are needed.  All that's needed is if you have an existing datetime object, d1, you can do:

s = str(d1)
d2 = datetime.datetime(s)
assert d1 == d2

for all values of d1.

But, let's at least agree on that.  Or, in the alternative, agree on something else.  Then we know what we're shooting for.
History
Date User Action Args
2012-09-09 12:15:03roysmithsetrecipients: + roysmith, belopolsky, nagle, Arfrever, r.david.murray, cvrebert, Alexander.Belopolsky
2012-09-09 12:15:03roysmithsetmessageid: <1347192903.1.0.815479107193.issue15873@psf.upfronthosting.co.za>
2012-09-09 12:15:02roysmithlinkissue15873 messages
2012-09-09 12:15:02roysmithcreate