➜

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 vstinner
Recipients Arfrever, Martin.Morrison, Matthew.Earl, belopolsky, hynek, pconnell, pitrou, swalker, vstinner
Date 2013-10-24.11:21:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382613709.68.0.35310137388.issue19376@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't think that the issue can be called a bug. If we pick another year (ex: 1904), you cannot compare two datetimes anymore:
"This solution has some very undesirable properties - namely that Mar 1st is now less than Feb 29th!"
http://bugs.python.org/issue14157#msg160637

If you want to handle "Feb 29", add an explicit year.

This issue is maybe a documentation issue: datetime.datetime.strptime() should warn users that calling datetime.datetime.strptime() without year may fail for Feb 29.
History
Date User Action Args
2013-10-24 11:21:49vstinnersetrecipients: + vstinner, belopolsky, pitrou, Arfrever, swalker, hynek, Martin.Morrison, pconnell, Matthew.Earl
2013-10-24 11:21:49vstinnersetmessageid: <1382613709.68.0.35310137388.issue19376@psf.upfronthosting.co.za>
2013-10-24 11:21:49vstinnerlinkissue19376 messages
2013-10-24 11:21:49vstinnercreate