Message254081
| Author |
xiang.zhang |
| Recipients |
Sean.Wang, martin.panter, paul.moore, steve.dower, tim.golden, xiang.zhang, zach.ware |
| Date |
2015年11月05日.03:59:17 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1446695958.34.0.851039709868.issue25534@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I'm afraid we can't say negative epoch is handled successfully on Linux.
Use $ touch -d "1 Jan 1900" test as a test, time.gmtime(os.fstat(f.fileno()).st_mtime) gives time.struct_time(tm_year=1899, tm_mon=12, tm_mday=31, tm_hour=15, tm_min=54, tm_sec=17, tm_wday=6, tm_yday=365, tm_isdst=0), which does not equals "1 Jan 1900". I think this is caused by python gmtime directly uses gmtime in C. Use the epoch of "1 Jan 1900" with C's gmtime does not give a right result. And while I am searching, I can not find any evidence that gmtime in C can give a right result with a negtive epoch.
And when I try the epoch of "1 Jan 1900" with "date -d @", it can generate the right result. |
|