Author belopolsky
Recipients Martin.Morrison, belopolsky, hynek, vstinner
Date 2012-02-29.15:48:41
SpamBayes Score 3.24656e-07
Marked as misclassified No
Message-id <1330530522.1.0.28036439577.issue14157@psf.upfronthosting.co.za>
In-reply-to
Content
This strikes me as an implementation artifact.  There is no reason for time.strptime() to validate date triplets.  Applications that require valid dates can use datetime.strptime().  I suggest changing time.strptime() specification to match POSIX strptime().  My understanding is that POSIX only requires field by field range checking (%d range 01 to 31, %m range 01 to 12) and not full structure validation.  This would be consistent with the way leap seconds are currently treated:

>>> time.strptime('60', '%S')[5]
60
History
Date User Action Args
2012-02-29 15:48:42belopolskysetrecipients: + belopolsky, vstinner, hynek, Martin.Morrison
2012-02-29 15:48:42belopolskysetmessageid: <1330530522.1.0.28036439577.issue14157@psf.upfronthosting.co.za>
2012-02-29 15:48:41belopolskylinkissue14157 messages
2012-02-29 15:48:41belopolskycreate