| commit | caebe22038d4de526ab34cfda98047f01c53fc9d | [log] [tgz] |
|---|---|---|
| author | Brett Cannon <bcannon@gmail.com> | Tue Jul 18 04:41:36 2006 +0000 |
| committer | Brett Cannon <bcannon@gmail.com> | Tue Jul 18 04:41:36 2006 +0000 |
| tree | 89516e1fc318b0b292a3774e707106cebc8bbaf5 | |
| parent | 4b7e35b530d06780ff905df2669ebdf892d6f75f [diff] |
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.