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 belopolsky, benno, davidfraser, eric.araujo, georg.brandl, giampaolo.rodola, kiorky, loewis, vstinner
Date 2011-01-07.22:59:32
SpamBayes Score 1.409663e-10
Marked as misclassified No
Message-id <>
After r87829 (see issue10827), the insane Y2K behavior of time module functions does not extend beyond year 999.  Hopefully in Python 3.3, accept2dyear will be removed completely and datetime.strftime() will be able to support the full intersection of platform year range with that of datetime type.  Meanwhile, I propose a simple patch that lowers the 1900 limit down to 1000.  I was not able to find any evidence that there are platforms that have issues with formatting years between 1000 and 1899.

Are there any objections to committing this patch?  I will monitor the build bots if I see failures, I'll modify the test and/or add a platform-specific check to fix them.
Date User Action Args
2011-01-07 22:59:49belopolskysetrecipients: + belopolsky, loewis, georg.brandl, davidfraser, benno, vstinner, giampaolo.rodola, eric.araujo, kiorky
2011-01-07 22:59:49belopolskysetmessageid: <>
2011-01-07 22:59:33belopolskylinkissue1777412 messages
2011-01-07 22:59:33belopolskycreate