]> granicus.if.org Git - python/commit
Python's strftime implementation does strange things with the year,
authorTim Peters <tim.peters@gmail.com>
Sun, 22 Dec 2002 20:34:46 +0000 (20:34 +0000)
committerTim Peters <tim.peters@gmail.com>
Sun, 22 Dec 2002 20:34:46 +0000 (20:34 +0000)
commit83b85f1d6cce999e0d85f669df71a520632a4c87
tree3a2fb24900f4ecaaf846bde6923dda0c42b14b69
parent14b6941197ca0368f78be6d87169047245f915b8
Python's strftime implementation does strange things with the year,
such that the datetime tests failed if the envar PYTHON2K was set.
This is an utter mess, and the datetime module's strftime functions
inherit it.  I suspect that, regardless of the PYTHON2K setting, and
regardless of platform limitations, the datetime strftime wrappers
will end up delivering nonsense results (or bogus exceptions) for
any year before 1900.  I should probably just refuse to accept years
earlier than that -- else we'll have to implement strftime() by hand.
Modules/datetimemodule.c