| commit | d2edcddc0a095d27c4f09a4c75894ed01ae94958 | |
| author | brett.cannon <brett.cannon@6015fed2-1504-0410-9fe1-9d1591cc4771> | |
| Tue, 18 Jul 2006 04:41:36 +0000 (18 04:41 +0000) | ||
| committer | brett.cannon <brett.cannon@6015fed2-1504-0410-9fe1-9d1591cc4771> | |
| Tue, 18 Jul 2006 04:41:36 +0000 (18 04:41 +0000) | ||
| tree | 97da170c7f1b4aea9829db4ecadeb981d0b971f2 | treesnapshot (tar.gz zip) |
| parent | f9733943a903fed7fefad3271558616fed797df0 | commitdiff |
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.
git-svn-id: http://svn.python.org/projects/python/trunk@50696 6015fed2-1504-0410-9fe1-9d1591cc4771
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.
git-svn-id: http://svn.python.org/projects/python/trunk@50696 6015fed2-1504-0410-9fe1-9d1591cc4771
| Doc/lib/libtime.tex | diffblobblamehistory | |
| Lib/test/test_time.py | diffblobblamehistory | |
| Misc/NEWS | diffblobblamehistory | |
| Modules/timemodule.c | diffblobblamehistory |