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 SilentGhost, Trundle, belopolsky, vstinner
Date 2011-01-04.18:30:45
SpamBayes Score 1.4162327e-07
Marked as misclassified No
Message-id <>
I am attaching a patch.  While working on the patch, I noticed that although time.accept2dyear is documented as boolean, the current code expects int and treats any non-int including True as 0:

>>> time.accept2dyear = True; time.asctime((99,) + (0,)*8)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: year >= 1900 required

>>> time.accept2dyear = 1; time.asctime((99,) + (0,)*8)
'Mon Jan  1 00:00:00 1999'

This is clearly a bug.  (Although Y2K note contradicts time.accept2dyear documentation.)

Supporting year < 1900 would be a feature in my view, but I agree with SilentGhost that once we extended support to 5+ digit years, it is odd to keep year >= 1900 restriction.
Date User Action Args
2011-01-04 18:30:47belopolskysetrecipients: + belopolsky, vstinner, Trundle, SilentGhost
2011-01-04 18:30:47belopolskysetmessageid: <>
2011-01-04 18:30:45belopolskylinkissue10827 messages
2011-01-04 18:30:45belopolskycreate