Message211616
> which is what I would expect based on the patch and the new AIX-specific error message. What did you expect?
No, mktime() and ctime() should both raise OverflowError. It looks like mktime() doesn't fail. Can you please try the following examples on AIX?
Examples on Linux:
>>> time.mktime((-100, 1, 10) + (0,)*6)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: year out of range
>>> time.mktime((100, 1, 10) + (0,)*6)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: year out of range
>>> time.mktime((1900, 1, 10) + (0,)*6)
-2208211761.0
>>> time.mktime((1930, 1, 10) + (0,)*6)
-1261526400.0
>>> time.mktime((1969,12,31, 23,59,59, 0,0,0))
-3601.0 |
|
Date |
User |
Action |
Args |
2014-02-19 13:35:57 | vstinner | set | recipients:
+ vstinner, serhiy.storchaka, David.Edelsohn |
2014-02-19 13:35:57 | vstinner | set | messageid: <1392816957.06.0.306492997544.issue19748@psf.upfronthosting.co.za> |
2014-02-19 13:35:57 | vstinner | link | issue19748 messages |
2014-02-19 13:35:56 | vstinner | create | |
|