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-08.01:08:57
SpamBayes Score 3.7701127e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
On Fri, Jan 7, 2011 at 7:26 PM, STINNER Victor <> wrote:
> Here is a patch removing the arbitrary datetime.strftime() limit on year: it adds an
> option "accept2dyear" to time.strftime() and datetime just sets this option to False.

The idea of adding an optional argument to  time.strftime() was
discussed on python-dev, but did not get much traction there:

I wish we didn't have to do that -- isn't it easy enough for the app
to do the 2d -> 4d conversion itself before calling the library
function? The only exception would be when parsing a string -- but
strptime can tell whether a 2d or 4d year is requested by the format
code (%y or %Y).
Date User Action Args
2011-01-08 01:09:05belopolskysetrecipients: + belopolsky, loewis, georg.brandl, davidfraser, benno, vstinner, giampaolo.rodola, eric.araujo, kiorky
2011-01-08 01:08:57belopolskylinkissue1777412 messages
2011-01-08 01:08:57belopolskycreate