Message116723
After further investigation, it appears the cause is the ability to overflow the datetime object by almost a year. I've modified the test to demonstrate this relative to the current date:
from datetime import date, datetime, timedelta
(datetime.now()-timedelta((date.today()-date(1,1,1)).days+364)).ctime()
It seems the date can be overflowed by up to a year without throwing an Exception. The result of which is a seg fault when calling the bound ctime method.
Note that anything above 364 results in OverFlowError. Below 18 still overflows, but does not seg fault, instead resulting in a weird result,e.g.:
'Tue (null) 240 17:25:37 0001'
I'll update the script to demonstrate the edge cases where this occurs. |
|
Date |
User |
Action |
Args |
2010-09-17 21:31:58 | bernie9998 | set | recipients:
+ bernie9998, barry, mark.dickinson, belopolsky, r.david.murray |
2010-09-17 21:31:57 | bernie9998 | set | messageid: <1284759117.95.0.331779490259.issue9888@psf.upfronthosting.co.za> |
2010-09-17 21:31:56 | bernie9998 | link | issue9888 messages |
2010-09-17 21:31:56 | bernie9998 | create | |
|