]> granicus.if.org Git - python/commit
Fix bug #1520914. Starting in 2.4, time.strftime() began to check the bounds
authorBrett Cannon <bcannon@gmail.com>
Tue, 18 Jul 2006 04:41:36 +0000 (04:41 +0000)
committerBrett Cannon <bcannon@gmail.com>
Tue, 18 Jul 2006 04:41:36 +0000 (04:41 +0000)
commitcaebe22038d4de526ab34cfda98047f01c53fc9d
tree89516e1fc318b0b292a3774e707106cebc8bbaf5
parent4b7e35b530d06780ff905df2669ebdf892d6f75f
Fix bug #1520914.  Starting in 2.4, time.strftime() began to check the bounds
of values in the time tuple passed in.  Unfortunately people came to rely on
undocumented behaviour of setting unneeded values to 0, regardless of if it was
within the valid range.  Now those values force the value internally to the
minimum value when 0 is passed in.
Doc/lib/libtime.tex
Lib/test/test_time.py
Misc/NEWS
Modules/timemodule.c