➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author CristiFati
Recipients CristiFati, steve.dower, tim.golden, zach.ware
Date 2015-04-14.11:56:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429012619.96.0.846306201826.issue23946@psf.upfronthosting.co.za>
In-reply-to
Content 
In WinPE environment (at least this is where I found it, but there might be cases where this issue could be spotted in normal Windows), some folders might have some of the FILETIME structures reset (because of RAMDrive?). When the conversion between WIN style (100 * nsecs from  1601/01/01) to UX style (secs from 1970/01/01) is taking place (epoch is being substracted), it could yield invalid filetime values (that will be reported by os.stat).

The attached patch simply goes around this initializing the UX timestamps to 0.

It was found in Python-2.7.3, the patch is for 2.7.8, but I think it can be reproduced with all the newer versions.
History
Date User Action Args
2015-04-14 11:56:59CristiFatisetrecipients: + CristiFati, tim.golden, zach.ware, steve.dower
2015-04-14 11:56:59CristiFatisetmessageid: <1429012619.96.0.846306201826.issue23946@psf.upfronthosting.co.za>
2015-04-14 11:56:59CristiFatilinkissue23946 messages
2015-04-14 11:56:59CristiFaticreate