Brett Cannon added the comment:
I agree with Victor: we should document that proper Feb 29/leap year support
requires a specified year, else constantly accepting Feb 29 as valid would lead
to more errors than fix.
--
nosy: +brett.cannon
___
Python t
STINNER Victor added the comment:
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/issue141
New submission from Matthew Earl:
datetime.datetime.strptime() without a year fails on Feb 29 with:
>>> datetime.datetime.strptime("Feb 29", "%b %d")
Traceback (most recent call last):
File "", line 1, in
File "/auto/ensoft-sjc/thirdparty/lib/python3.3/_strptime.py", line 511, in
_strptime
